Labels
In order to make it easier to identify objects that are all part of the same
conceptual pipeline, custom
labels
set on resources used by Tekton Pipelines are propagated from more general to
more specific resources, and a few labels are automatically added to make it
easier to identify relationships between those resources.
Propagation Details
For Pipelines
executed using a PipelineRun
, labels are propagated
automatically from Pipelines
to PipelineRuns
to TaskRuns
and then toPods
. Additionally, labels from the Tasks
referenced by TaskRuns
are
propagated to the corresponding TaskRuns
and then to Pods
.
For TaskRuns
executed directly, not as part of a Pipeline
, labels are
propagated from the referenced Task
(if one exists, see the
Specifying a Task
section of the TaskRun
documentation) to the corresponding TaskRun
and then to the Pod
.
Automatically Added Labels
The following labels are added to resources automatically:
tekton.dev/pipeline
is added toPipelineRuns
(and propagated toTaskRuns
andPods
), and contains the name of thePipeline
that thePipelineRun
references.tekton.dev/pipelineRun
is added toTaskRuns
(and propagated toTaskRuns
andPods
) that are created automatically during the execution of aPipelineRun
, and contains the name of thePipelineRun
that triggered the
creation of theTaskRun
.tekton.dev/task
is added toTaskRuns
(and propagated toPods
) that
reference an existingTask
(see the
Specifying aTask
section of theTaskRun
documentation), and contains the name of theTask
that theTaskRun
references.tekton.dev/taskRun
is added toPods
, and contains the name of theTaskRun
that created thePod
.
Examples
Finding Pods for a Specific PipelineRun
To find all Pods
created by a PipelineRun
named test-pipelinerun, you could
use the following command:
kubectl get pods --all-namespaces -l tekton.dev/pipelineRun=test-pipelinerun
Finding TaskRuns for a Specific Task
To find all TaskRuns
that reference a Task
named test-task, you could use
the following command:
kubectl get taskruns --all-namespaces -l tekton.dev/task=test-task