Aaryan123456679 commented on PR #70238: URL: https://github.com/apache/airflow/pull/70238#issuecomment-5066615349
Thanks for the suggestion — that's a cleaner approach. I've reworked the PR accordingly: - Added a `securityContexts.disableDefaults` flag (default `false`). When set, the chart no longer fills in the default `runAsUser`/`fsGroup` (pod) or `runAsUser` (container) values wherever `securityContexts.pod` / `securityContexts.containers` (or the per-component overrides) are left empty — the `securityContext` key is omitted from the rendered manifest entirely, rather than emitting an explicit `null`. - Reverted the `values.schema.json` change back to the vendored `io.k8s.api.core.v1.PodSecurityContext` ref (dropped the earlier `AirflowPodSecurityContext` nullable-fields workaround), since the flag makes that special-casing unnecessary. - Explicit values in `securityContexts.pod` / `securityContexts.containers` (global or per-component) still take priority over `disableDefaults`, so existing fine-grained overrides are unaffected. - Updated the newsfragment, `production-guide.rst`, and `test_security_context.py` to describe the flag instead of the null-based workaround. Let me know if this matches what you had in mind, or if you'd adjust the flag's scope or naming. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
