feat(helm): add pod-level securityContext support for certificate mounting #19041
+468
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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