Feature Request: Support for secret key files via volume mounts
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 24
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
RustFS recently added support for specifying access_key and secret_key via files instead of environment variables (rustfs/rustfs#1814). This is more secure as env vars can leak through /proc//environ or debug endpoints.
Currently the chart only supports secrets as env vars (secret.existingSecret / secret.rustfs.access_key). There's no way to mount a secret as a file and reference it via the new key file flags.
It would be great to have either:
extraVolumes / extraVolumeMounts support (general-purpose), or
a dedicated secret.keyFile option that mounts the existing secret as files and passes the appropriate flags
This would allow Kubernetes users to leverage the key file feature from #1814 without patching the chart.
Contributor guide
No contributing guide indexed for this repository
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 inspecting the chart configuration for secret.existingSecret and secret.rustfs.access_key, then read RustFS #1814 for the key-file flags. Decide whether general extraVolumes/extraVolumeMounts or a dedicated secret.keyFile option fits the chart; done means users can mount an existing secret as files and pass the corresponding flags without environment variables.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100