Allow sssd.conf ldap_default_authtok to reference a kubernetes secret
Open
Nobody has claimed this yet.
team: workbench
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
Currently, this password, whether encrypted or unencrypted must be passed as a raw value in the userProvisioning section of the chart, which limits the transportability of this chart and prevents/restricts the ability for administrators to check their values.yaml into version control.
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 by locating the chart's userProvisioning section and the sssd.conf configuration referenced by the issue, then inspect how values.yaml currently supplies ldap_default_authtok. Define done as allowing that password to come from a Kubernetes Secret instead of requiring a raw value in values.yaml, while preserving the existing configuration path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100