- Notifications
You must be signed in to change notification settings - Fork1k
feat(helm): add pod-level securityContext support for certificate mounting#19041
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
github-actionsbot commentedJul 24, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
All contributors have signed the CLA ✍️ ✅ |
I have read the CLA Document and I hereby sign the CLA |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
This PR looks really solid to me, +1
faac753
intomainUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Add pod-level securityContext support to Coder Helm chart
Adds
coder.podSecurityContext
field to enable pod-level security settings, primarily to solve TLS certificate mounting permission issues.Problem: When mounting TLS certificates from Kubernetes secrets, the Coder process (UID 1000) cannot read the files due to restrictive permissions.
Solution: Setting
podSecurityContext.fsGroup: 1000
ensures Kubernetes sets group ownership of mounted volumes to GID 1000, allowing the Coder process to read certificate files.Changes:
podSecurityContext
field to values.yaml with documentation_coder.yaml
template to include pod-level security contextUsage:
Fixes#19038