Launch Pod/job in separate namespace and support in helm chart

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?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct