Should the compiler generate Pipeline or PipelineRun

This is a general discussion, not a work item.

Conceptually a Pipeline is a static specification orchestrating how a set of Tasks should be executed. A PipelineRun is an instantiation of a pipeline. A pipeline is a re-usable artifact that can be “run” repeatedly, a pipeline-run is one-and-done.

Currently the KFP-Tekton compiler generates a YAML with (multiple) Tasks(s) and one Pipeline document. There are however certain features supported by the KFP DSL which are not easily transferred into an equivalent feature in Tekton Pipelines, but instead require the concept of a PipelineRun, like mounting PVC volume to a pipeline workspace or setting a timeout at the pipeline level.

Linked issues

• Pipeline level timeout #56
• Passing parameters between tasks #41
• Volume mounts #51
• Generate PipelineRun with embedded pipelineSpec and taskSpec #143

[ckadner]

PipelineRun with Pipeline definition embed

I think @Tomcli 's approach (PR #62) with generating an optional PipelineRun in addition to the existing Pipeline with Tasks will be the best compromise and allows to keep existing code intact. At least for the time being.

[k8s-ci-robot]

@Tomcli: Closing this issue.

In response to this:

Thanks @Udiknedormin /close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.