Tekton Resource

Internal

• Tekton Concepts

Overview

• Understand the relationship between Resources and PipelineResources.
• Understand transition from PipelineResources to Tasks, read https://tekton.dev/docs/pipelines/migrating-v1alpha1-to-v1beta1/#replacing-pipelineresources-with-tasks
• Parse https://tekton.dev/docs/pipelines/resources/ and map it on the new implementation.

Resources are used to share data between steps and tasks, and depending on which direction they are looked at, the can be input or output resources. Resources are connected to tasks and pipelines by taskRuns and pipelineRuns, respectively. A run must include the actual addresses of resources, such as the URLs of repositories, its task or pipeline needs.

Example of resources:

• git repository
• a pull request
• a container image
• a Kubernetes cluster
• storage: an object, a directory, etc.
• a CloudEvent

Input Resource

The input is defined relative to a step. Examples of input resources are: git repository.

Output Resource

The output is defined relative to a step. Examples of output resources: container image.

PipelineResource

Deprecated. Defines locations for inputs ingested and outputs produced by the steps in tasks. Also see Task Resources.

TO PROCESS:

• The from field: https://tekton.dev/docs/pipelines/pipelines/#using-the-from-field
• https://tekton.dev/docs/pipelines/resources/