Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add variable substitution to fields within a Projected Volume #2597

Closed
jlpettersson opened this issue May 11, 2020 · 0 comments · Fixed by #2601
Closed

Add variable substitution to fields within a Projected Volume #2597

jlpettersson opened this issue May 11, 2020 · 0 comments · Fixed by #2601
Assignees
@jlpettersson
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@jlpettersson
Copy link
Member

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
@tekton-robot tekton-robot added the kind/feature Categorizes issue or PR as related to a new feature. label May 11, 2020
jlpettersson added a commit to jlpettersson/pipeline that referenced this issue May 11, 2020
@jlpettersson
Add variable expansion for params in Projected Volume fields
53d6395 
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 jlpettersson mentioned this issue May 11, 2020
Merged
3 tasks
jlpettersson added a commit to jlpettersson/pipeline that referenced this issue May 12, 2020
@jlpettersson
Add variable expansion for params in Projected Volume fields
df7e19e 
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
@jlpettersson
Add variable expansion for params in Projected Volume fields
4d2babc 
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
@jlpettersson
Add variable expansion for params in Projected Volume fields
4215ec5 
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
@jlpettersson @tekton-robot
Add variable expansion for params in Projected Volume fields
fc24674 
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
Assignees

@jlpettersson jlpettersson

Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add variable expansion for params in Projected Volume fields jlpettersson/pipeline
2 participants
@jlpettersson @tekton-robot