-
Notifications
You must be signed in to change notification settings - Fork 16.4k
fix: add SCC to dag processor #51080
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.
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
Conversation
|
Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
|
chart/templates/rbac/security-context-constraint-rolebinding.yaml
Outdated
Show resolved
Hide resolved
|
Thanks for the PR @kesem0811. Can you add test coverage here? (There might be more places in that file as well) |
bb5f079 to
699bb39
Compare
|
Needs rebase |
* fix: add SCC to dag processor * delete typing error * your message * change my test * change the value deffault * fix tests2 * fix tests2 * return values to original version * run ruff formater * change the SCC tests * change the SCC tests * fix formatting
helm: Add SCC role binding for dag-processor service account
Currently, the Airflow Helm chart includes a template that creates SCC (Security Context Constraints) role bindings for the service accounts of all components—except the dag-processor.
This PR adds an SCC role binding for the dag-processor service account to ensure consistent security configuration across all Airflow components.
This change is required in environments that use the dag-processor component together with SCC policies, such as OpenShift or other restricted Kubernetes clusters. Without this binding, the dag-processor may fail to start due to insufficient security privileges.