-
Notifications
You must be signed in to change notification settings - Fork 249
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
Add workspace when starting a pipeline or task #651
Comments
/kind feature |
maybe we can have a workspace backed by configmap if no pvc is specified? |
/cc @sbwsg |
We also are discussing having an "auto" workspace just in case the user doesn't want / know how to provide one. This would be something the pipeline controller injects in response to some config and would work similarly to how pipeline resources have a PVC generated for them today (called the "artifacts pvc"), but would be more transparent to the user (hopefully). |
Auto workspace is very useful. Still makes sense to allow users to override it but it would definitely simplify starting pipelines. |
It could be something like:
|
/assign khrm |
Given the workspace support in pipelines, currently one has to create a
PipelineRun
yaml in order to start a pipeline that requires a workspace. Thetkn pipeline start
command should be augmented to be able to map persistent volume claims to workspace when starting a pipeline.Suggestion:
The above syntax is similar to pipeline resources
The text was updated successfully, but these errors were encountered: