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

Create taskrun/pipelinerun from oci bundle #1474

Open
vdemeester opened this issue Dec 14, 2021 · 3 comments
Open

Create taskrun/pipelinerun from oci bundle #1474

vdemeester opened this issue Dec 14, 2021 · 3 comments
Labels
area/roadmap Issues that are part of the project (or organization) roadmap (usually an epic) kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@vdemeester
Copy link
Member

Feature request

It should be possible to create a TaskRun (using tkn task start) from a oci bundle.
Today, we can create a TaskRun from an in-cluster Task definition. If oci bundles are enabled on a Pipeline instance, it's possible to create a TaskRun that uses the oci bundle image reference as Task definition reference. It should be possible to do that from the cli directly

The same should be possible for PipelineRun as well

Use case

Use oci bundle from the cli 👼🏼

UI Example

$ tkn task start oci://quay.io/vdemeest/my-task:0.1 -p foo=bar …
@vdemeester vdemeester added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 14, 2021
@tekton-robot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 14, 2022
@vdemeester
Copy link
Member Author

/remove-lifecycle stale
/area roadmap
/lifecycle frozen

@tekton-robot tekton-robot added area/roadmap Issues that are part of the project (or organization) roadmap (usually an epic) lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 14, 2022
@digglife
Copy link
Contributor

There could be multiple layers(tasks) in one bundle image, do we need to cover that? Or we can assume there is only one task?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/roadmap Issues that are part of the project (or organization) roadmap (usually an epic) kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
Status: Todo
Development

No branches or pull requests

3 participants