You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
security(cilium): give Hubble relay and UI the two C-0211 defaults #4090
The 2026-09-23 re-measurement on #3239 found 8 controllers in kube-system still missing the two non-privilege C-0211 defaults. Six come from the Cilium HelmRelease. Two of them, hubble-relay and hubble-ui, are off the data path.
Change
Set fsGroupChangePolicy: OnRootMismatch on both pods and an empty seLinuxOptions on every container, using chart values. Helm merges these into the chart's own security defaults, so no privilege, user or group field changes.
Acceptance criteria
A render test on the pinned chart proves that both Deployments carry the two fields, that the chart's own hardening is kept, and that nothing else in the render changes.
After rollout, both live Deployments carry the fields and their pods are Ready.
Size: small. The Cilium agent, operator, Envoy and the certgen CronJob come in later slices.
Verified live after platform#4091 rolled out: hubble-relay (2/2 ready) and hubble-ui (1/1 ready) both carry fsGroupChangePolicy: OnRootMismatch at pod level and seLinuxOptions: {} on every container (relay, frontend, backend). The remaining cilium components stay tracked on #3239.
Activity
devantler commentedon Sep 23, 2026
Verified live after platform#4091 rolled out:
hubble-relay(2/2 ready) andhubble-ui(1/1 ready) both carryfsGroupChangePolicy: OnRootMismatchat pod level andseLinuxOptions: {}on every container (relay, frontend, backend). The remaining cilium components stay tracked on #3239.