Add explicit support for client secrets by volume mount.
Open
Nobody has claimed this yet.
team: workbench
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
Description
Similar to this PR: https://github.com/rstudio/helm/pull/726
We suggest,
- Storing secrets as kubernetes secrets.
- Mounting the secrets into the container by volume mount.
We have a few secrets which are not explicitly supported in helm in this way - including the openid client secret. So we should add support for that as well.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the related pull request 726 and the chart's existing secret configuration first. Define the required OpenID client-secret volume-mount configuration, then verify that the secret can be stored as a Kubernetes Secret and mounted into the container without exposing it as an unsupported Helm value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- authentication, devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100