Multi namespace resources do not exist for airflow tasks to run on new namespace

[shaked-tech]

Checks

• I have checked for existing issues.
• This report is about the User-Community Airflow Helm Chart.

Chart Version

1.16.0

Kubernetes Version

Client Version: v1.30.1
Server Version: v1.30.4

Helm Version

version.BuildInfo{Version:"v3.18.3", GitCommit:"6838ebcf265a3842d1433956e8a622e3290cf324", GitTreeState:"clean", GoVersion:"go1.24.4"}

Description

Recreated the required resources from the main namespace 'airflow', now pods (tasks) are running
The resources are -

serviceaccount:
airflow-worker
configmap:
airflow-config
secrets:
airflow-fernet-key
airflow-metadata
airflow-webserver-secret-key

how am i to use this multi namespace feature if helm does not take care of creation and updating the resources required by the task pods??

Relevant Logs

resource not found ...

Custom Helm Values

multiNamespaceMode: true
config:
  kubernetes_executor:
    namespace: airflow-jobs

[shaked-tech]

Am i the only one 'trying' using the multi namespace feature?

[stale]

This issue has been automatically marked as stale because it has not had activity in 60 days.
It will be closed in 7 days if no further activity occurs.

Thank you for your contributions.

---

Issues never become stale if any of the following is true:

1. they are added to a Project
2. they are added to a Milestone
3. they have the lifecycle/frozen label