-
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
Consider better use of ProjectedVolumes #3551
Comments
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
/remove-lifecycle stale |
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. |
/remove-lifecycle rotten in v1 planning - #3548 |
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 |
Feature request
ProjectedVolumes is very useful, both for Secrets, ConfigMaps and modern ServiceAccounts. The way Tekton currently supports ServiceAccounts should be considered outdated - since the tokens are not rotated and less secure than the new solution, Service Account Token Volume Projection using ProjectedVolumes.
Use case
At least ServiceAccounts should preferrably be used from a ProjectedVolume. Currently this is a bit clumsy - through the taskRunSpecs. We could consider a better API - potentially via Workspaces?
Also see No More Forever Tokens: Changes in Identity Management for Kubernetes.
Some of these APIs will be upgraded (possibly to GA?) in v1.20
The text was updated successfully, but these errors were encountered: