Add variable substitution to fields within a Projected Volume #2597
Assignees
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
Comments
tekton-robot
added
the
kind/feature
jlpettersson
added a commit
to jlpettersson/pipeline
that referenced
this issue
May 11, 2020
A [projected volume](https://kubernetes.io/docs/concepts/storage/volumes/#projected) can mount/project files from `Secrets`, `ConfigMaps` and `ServiceAccountTokens`. Is is good if the end user can choose the name of `Secrets`, `ConfigMaps` and the audience of `ServiceAccountTokens`. With this commit, the task author can use `params` for `secret.name`, `configmap.name` and `serviceaccounttoken.audience` in a Projected Volume. See examples of use cases in tektoncd#2597 Fixes tektoncd#2597
3 tasks
jlpettersson
added a commit
to jlpettersson/pipeline
that referenced
this issue
May 12, 2020
A [projected volume](https://kubernetes.io/docs/concepts/storage/volumes/#projected) can mount/project files from `Secrets`, `ConfigMaps` and `ServiceAccountTokens`. Is is good if the end user can choose the name of `Secrets`, `ConfigMaps` and the audience of `ServiceAccountTokens`. With this commit, the task author can use `params` for `secret.name`, `configmap.name` and `serviceaccounttoken.audience` in a Projected Volume. See examples of use cases in tektoncd#2597 Fixes tektoncd#2597
jlpettersson
added a commit
to jlpettersson/pipeline
that referenced
this issue
May 13, 2020
A [projected volume](https://kubernetes.io/docs/concepts/storage/volumes/#projected) can mount/project files from `Secrets`, `ConfigMaps` and `ServiceAccountTokens`. Is is good if the end user can choose the name of `Secrets`, `ConfigMaps` and the audience of `ServiceAccountTokens`. With this commit, the task author can use `params` for `secret.name`, `configmap.name` and `serviceaccounttoken.audience` in a Projected Volume. See examples of use cases in tektoncd#2597 Fixes tektoncd#2597
jlpettersson
added a commit
to jlpettersson/pipeline
that referenced
this issue
May 20, 2020
A [projected volume](https://kubernetes.io/docs/concepts/storage/volumes/#projected) can mount/project files from `Secrets`, `ConfigMaps` and `ServiceAccountTokens`. Is is good if the end user can choose the name of `Secrets`, `ConfigMaps` and the audience of `ServiceAccountTokens`. With this commit, the task author can use `params` for `secret.name`, `configmap.name` and `serviceaccounttoken.audience` in a Projected Volume. See examples of use cases in tektoncd#2597 Fixes tektoncd#2597
tekton-robot
pushed a commit
that referenced
this issue
May 22, 2020
A [projected volume](https://kubernetes.io/docs/concepts/storage/volumes/#projected) can mount/project files from `Secrets`, `ConfigMaps` and `ServiceAccountTokens`. Is is good if the end user can choose the name of `Secrets`, `ConfigMaps` and the audience of `ServiceAccountTokens`. With this commit, the task author can use `params` for `secret.name`, `configmap.name` and `serviceaccounttoken.audience` in a Projected Volume. See examples of use cases in #2597 Fixes #2597
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
That I can use projected volumes, e.g. for more secure ServiceAccountTokens (that expire and may have single-audience), or using a Secret or ConfigMap mounted to a single directory.
I also want to name my Secret, ConfigMap and ServiceAccountToken how I want in my environment.
Proposal
Add variable substitution for the most common fields within a Project Volume.
Use cases:
/kind feature
/assign
The text was updated successfully, but these errors were encountered: