mikebell90 opened a new issue, #25222: URL: https://github.com/apache/airflow/issues/25222
### Description Our engineers want to run jobs in a separate namespace from the installed release via helm chart. It looks to me like right now the rbac configuration has two choices * multicluster - generates ClusterRole * !multicluster - generales rolebinding in RELEASE namespace. Why these don't work for us * multicluster is too wide, we want to restrict the namespace * !multicluster - I think only lets stuff be generated in the same namespace? Or will airflow be able to generate pods in another namespace Sorry for the ignorant questions - don't really know airflow, just trying to help out the engineers. ### Use case/motivation Our engineers want to run jobs in a separate namespace from the installed release via helm chart. ### Related issues There are some about pod override of namespace, I'm not sure due to inexperience with Airflow ### Are you willing to submit a PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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: commits-unsubscr...@airflow.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
