Set the OIDC client secret in an existingSecret in the helm chart
Open
Nobody has claimed this yet.
enhancement
help wanted
- Dominant language
- Mustache
- Stars
- 197
- Forks
- 104
- Avg merge
- 22m
- Merged PRs (30d)
- 2
Description
Steps to reproduce the problem
Install from helm chart.
Expected behaviour
The oidc client secret should be set in an existing secret for extra security (on par with the rest of the secure tokens)
Actual behaviour
You need to set it in the values
Detailed description
I've created a pull request to fix this: https://github.com/mastodon/mastodon/pull/20803
Specifications
v3.5.5
v4.0.2
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
Start in the Helm chart's values and OIDC configuration, comparing how the chart handles other secure tokens through existing secrets. Render or install the chart with an existing secret; the work is done when the OIDC client secret can come from that secret instead of being stored directly in values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100