Skip to content

fix(charts): streaming-hub values header still claimed fsGroup replaces the pod security context #1804

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
fredcamaral merged 1 commit into from
Jul 31, 2026
Merged

fix(charts): streaming-hub values header still claimed fsGroup replaces the pod security context #1804

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions charts/streaming-hub/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -445,8 +445,10 @@ streamingHub:
# kubernetes.io/tls (keys tls.crt / tls.key) named by certificateSecretName —
# in the Lerian environments a cert-manager Certificate in the deploying overlay
# creates it. fsGroup 65532 is applied to the pod so the sidecar's non-root user
# can read the 0440 projection; that REPLACES streamingHub.podSecurityContext
# while rolesAnywhere is enabled.
# can read the 0440 projection; it is MERGED into streamingHub.podSecurityContext
# while rolesAnywhere is enabled — fsGroup wins, and every other pod-level setting
# you configured (runAsNonRoot, seccompProfile, supplementalGroups, ...) survives.
# It used to replace the block wholesale, silently dropping all of them.
#
# trustAnchorArn / profileArn / roleArn are `required` when enabled — the chart
# fails to render rather than starting a sidecar that cannot authenticate.
Expand Down
Loading