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
I am deploying Airflow using the official Helm chart in an OpenShift environment, where I've run into a configuration challenge. The security constraints in our OpenShift setup can vary significantly between namespaces, and even within a single namespace over time. This variability can be due to policy changes or specific needs during disaster recovery scenarios, such as changes in UID constraints.
Currently, the values.schema.json in the Airflow Helm chart does not support setting the security constraints to "null," which restricts our ability to dynamically adjust these settings based on the environmental context.
Is there a recommended approach to handle such dynamic security constraints within the Airflow Helm chart? Has anyone successfully implemented a flexible solution to this in similar environments? I'm looking for guidance or potential workarounds that could be applied to adapt the Helm chart for dynamic security settings.
Thank you in advance for your insights and suggestions!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello Apache Airflow Community,
I am deploying Airflow using the official Helm chart in an OpenShift environment, where I've run into a configuration challenge. The security constraints in our OpenShift setup can vary significantly between namespaces, and even within a single namespace over time. This variability can be due to policy changes or specific needs during disaster recovery scenarios, such as changes in UID constraints.
Currently, the values.schema.json in the Airflow Helm chart does not support setting the security constraints to "null," which restricts our ability to dynamically adjust these settings based on the environmental context.
Is there a recommended approach to handle such dynamic security constraints within the Airflow Helm chart? Has anyone successfully implemented a flexible solution to this in similar environments? I'm looking for guidance or potential workarounds that could be applied to adapt the Helm chart for dynamic security settings.
Thank you in advance for your insights and suggestions!
Beta Was this translation helpful? Give feedback.
All reactions