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
feat(chart): add securityContext, priorityClassName, and standard labels
Add support for Kubernetes security and scheduling best practices:
- Add configurable `podSecurityContext` (default: `fsGroup: 1000`,
preserving existing behavior) and `securityContext` for the container
(default: `{}`, no change for existing users)
- Add `priorityClassName` value (default: empty, field not emitted)
- Add standard `app.kubernetes.io/*` labels via helpers while keeping
the existing `app: <name>` selector labels for backwards compatibility
These changes allow deployments to comply with Kubernetes PodSecurity
"restricted" profile and common policy engines (Kyverno, OPA/Gatekeeper)
without breaking existing installations.
Selector labels (`spec.selector.matchLabels`) are intentionally left
unchanged to avoid breaking rolling updates on existing deployments.
Example values for PodSecurity "restricted" compliance:
securityContext:
runAsNonRoot: true
allowPrivilegeEscalation: false
capabilities:
drop: ["ALL"]
seccompProfile:
type: RuntimeDefault
priorityClassName: my-priority-class
0 commit comments