In Tekton, what would you create to encapsulate a single, reusable unit of work?

In Tekton, what would you create to encapsulate a single, reusable unit of work?

• A. PipelineRun
• B. TaskRun
• C. Pipeline
• D. Task

Answer: (D)

A Task in Tekton is the primitive that encapsulates a single, reusable unit of work. It defines the set of steps to run, along with any parameters, workspaces, and resources it needs, so you can reuse that exact unit in different pipelines or across multiple pipelines. A Task remains the same while you can create many TaskRuns to execute it with different inputs or contexts. A TaskRun, by contrast, is just an execution of a Task. It records how that Task was run, including status and results, but it isn’t the reusable unit itself. A Pipeline is a collection of Tasks that defines a workflow, and a PipelineRun is what triggers the execution of that Pipeline. So the single, reusable unit of work you would create is a Task.

A Task in Tekton is the primitive that encapsulates a single, reusable unit of work. It defines the set of steps to run, along with any parameters, workspaces, and resources it needs, so you can reuse that exact unit in different pipelines or across multiple pipelines. A Task remains the same while you can create many TaskRuns to execute it with different inputs or contexts.

A TaskRun, by contrast, is just an execution of a Task. It records how that Task was run, including status and results, but it isn’t the reusable unit itself. A Pipeline is a collection of Tasks that defines a workflow, and a PipelineRun is what triggers the execution of that Pipeline.

So the single, reusable unit of work you would create is a Task.