GitHub user attilaolah created a discussion: feat(helm): improve restricted security context support
Please provide a way to apply restrictive security contexts consistently to all chart-managed pods and containers, including init jobs and built-in init containers. Ideally, the chart could ship restricted-compatible defaults out of the box: - `runAsNonRoot: true` - `allowPrivilegeEscalation: false` - `capabilities.drop: ["ALL"]` - `seccompProfile.type: RuntimeDefault` - non-root UID/GID where supported by the image At minimum, please add values that let users set default pod/container security contexts for every workload and every built-in init container without replacing upstream init container definitions. This would make the chart easier to run in namespaces enforcing Kubernetes `restricted` Pod Security. GitHub link: https://github.com/apache/superset/discussions/42124 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
