Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generate PipelineRun with embedded pipelineSpec and taskSpec #143

Closed
ckadner opened this issue May 8, 2020 · 5 comments · Fixed by #166
Closed

Generate PipelineRun with embedded pipelineSpec and taskSpec #143

ckadner opened this issue May 8, 2020 · 5 comments · Fixed by #166

Comments

@ckadner
Copy link
Member

ckadner commented May 8, 2020

/kind feature

Description:
Convert the YAML produced by the kfp-tekton compiler:

  • from multiple documents (Conditions, Tasks, Pipeline, PipelineRun) into
  • into a single PipelineRun with embedded pipelineSpec and taskSpecs

This will simply the required work for down-stream integration with the KFP API and KFP UI.

Additional information:

spec:
  pipelineSpec:
    tasks:
    - name: task1
      taskSpec:
        steps:
          ...
@issue-label-bot
Copy link

Issue Label Bot is not confident enough to auto-label this issue.
See dashboard for more details.

1 similar comment
@issue-label-bot
Copy link

Issue Label Bot is not confident enough to auto-label this issue.
See dashboard for more details.

@ckadner ckadner changed the title Generate PipelineRun with embedded pipelineSpec and taskSpec Generate PipelineRun with embedded pipelineSpec and taskSpec May 8, 2020
@ckadner
Copy link
Member Author

ckadner commented May 8, 2020

@afrittoli -- do you know if there are any functional limitations with using embedded pipelineSpec and taskSpec?

We are evaluating if the kfp-tekton compiler could generate one single document including Conditions.

@Tomcli
Copy link
Member

Tomcli commented May 8, 2020

@afrittoli pipelineSpec and taskSpec works well on pipelineRun. However, I couldn't find the conditionSpec in the pipelineRun v1beta1 CRD, is it because conditions are still in v1alpha1 API?

@animeshsingh
Copy link
Collaborator

Is there anything else besides pipelineSpec, taskSpec and conditionSpec ?

@animeshsingh animeshsingh reopened this May 10, 2020
ckadner added a commit to ckadner/kfp-tekton that referenced this issue Jun 1, 2020
ckadner added a commit to ckadner/kfp-tekton that referenced this issue Jun 16, 2020
ckadner added a commit to ckadner/kfp-tekton that referenced this issue Jun 16, 2020
ckadner added a commit to ckadner/kfp-tekton that referenced this issue Jun 16, 2020
ckadner added a commit to ckadner/kfp-tekton that referenced this issue Jun 16, 2020
ckadner added a commit to ckadner/kfp-tekton that referenced this issue Jun 16, 2020
ckadner added a commit to ckadner/kfp-tekton that referenced this issue Jun 17, 2020
ckadner added a commit to ckadner/kfp-tekton that referenced this issue Jun 23, 2020
k8s-ci-robot pushed a commit that referenced this issue Jun 24, 2020
* PipelineRun with embedded pipelineSpec and taskSpec

Closes #143

* Preserve empty string default values

* Remove success_condition and failure_condition
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants