Do not use subPath for config volumeMounts
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
As is very briefly mentioned in the docs, kubernetes unfortunately does not support automatically updating volumes mounted with subPath when the underlying ConfigMap changes. This can cause quite the trouble when trying do upgrade Nextcloud via GitOps with configs supplied via Helm values.
Perhaps we could find a solution that mounts the ConfigMap in its entirety to a directory?
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 reading the linked Kubernetes documentation on ConfigMap updates and inspecting charts/nextcloud/templates/deployment.yaml around line 264. Determine how the config volumeMount uses subPath and evaluate a directory-based mount approach; done means ConfigMap changes can update the mounted configuration during upgrades.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100