Pipeline runs are to pipelines what task runs are to tasks. They are the actual executions of the pipelines.

Using the pipeline used in the last section, let's create a new pipeline run and examine the output:

$ tkn pipeline start results 
? Value for param `sides` of type `string`? (Default is `6`) 6 
PipelineRun started: results-run-sb6lk 
  
In order to track the PipelineRun progress run: 
tkn pipelinerun logs results-run-sb6lk -f -n default 

You can see that when you run the tkn pipeline start command, it generates a pipeline run with a random name. In this case, the name is results-run-sb6lk. To see the output of the run, you will use the tkn CLI tool to visualize the logs of this specific pipeline run.

Because pipeline runs are Kubernetes objects, you can manipulate them with kubectl the same way you would any other Kubernetes primitive. For example, you could use kubectl get to list all the pipeline runs that exist inside...