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
Cannot use parameter substitution for volume size #1514
Comments
/kind feature |
Is this more of a bug than a feature? |
It depends on how you interpret the doc, specifically: https://github.com/tektoncd/pipeline/blob/master/docs/tasks.md#variable-substitution and: https://github.com/tektoncd/pipeline/blob/master/docs/tasks.md#variable-substitution-within-volumes Nothing in the doc currently says that one can use variable substitution for volume characteristics. |
Thanks for reporting this! |
Related to #1530 |
I think we're tending toward moving away from specifying volumes in Tasks now that we have workspaces (and #2326 adds the ability to create volumes w/in a Run) - we even considered removing volumes altogether #2058. So I'm going to close this for now but please re-open if you feel like workspaces can't meet your needs (and/or open another issue with required features for workspaces!) Thanks @NicolasRouquette 🙏 |
Expected Behavior
Apply the following resource:
We should get:
Actual Behavior
Steps to Reproduce the Problem
kubectl apply -f <file>
where ` is the task described abovetkn tasks ls
Additional Info
This behavior suggests that it is currently not possible to define tekton parameters for cpu or memory characteristics (quota or limits). Are there other similar limitations?
The text was updated successfully, but these errors were encountered: