-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
CSI volumes as workspaces #4446
Comments
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
/lifecycle frozen |
/assign |
Feature request
Support kubernetes CSI volumes (https://kubernetes.io/docs/concepts/storage/volumes/#csi) as workspaces
Use case
My main motivation is to be able to use Secrets Store CSI Driver (https://secrets-store-csi-driver.sigs.k8s.io/introduction.html)
to use Hashicorp Vault (or any other secret provider) .
I want to be able to define a workspace in the following way:
Of course, there are other ways to mount secrets into the task's pods, but this way we can define tasks in a standard way (using workspaces) and select later the source of those workspaces.
The text was updated successfully, but these errors were encountered: