anzinmhd commented on issue #74850: URL: https://github.com/apache/airflow/issues/74850#issuecomment-6222772013
I reproduced this with Airflow **3.2.2**, `KubernetesExecutor`, and `multiNamespaceMode: true` on a local Kubernetes cluster. The scheduler, API server, Dag processor, and database ran in one namespace. A single-task Dag used a pod override to launch its worker in a separate namespace. I provided the worker's required ConfigMaps, service account, and other template-referenced Secrets, but left the metadata Secret absent. Observed results: - Without the metadata Secret in the worker namespace, the Airflow worker container remained in `CreateContainerConfigError`. Kubernetes reported `secret "repro322-metadata" not found`. - After adding that Secret with a correctly formatted PostgreSQL URI containing deliberately invalid credentials, a fresh Dag run completed successfully. The worker reported `exit_code=0` and `final_state=success` and used the Execution API. The apparent cause is the shared Helm environment helper. The [worker pod template](https://github.com/apache/airflow/blob/b9aa889577/chart/files/pod-template-file.kubernetes-helm-yaml#L125) includes `standard_airflow_environment`, which adds both `AIRFLOW__DATABASE__SQL_ALCHEMY_CONN` and `AIRFLOW_CONN_AIRFLOW_DB` as mandatory [metadata Secret references](https://github.com/apache/airflow/blob/b9aa889577/chart/templates/_helpers.yaml#L73). Kubernetes must resolve these references before starting the container, even though this Airflow 3 task does not need valid metadata database credentials. I also compared the local worker template, helper, and default values used for this reproduction with upstream `main` at `b9aa889577`; all three files are identical. This was a runtime test of Airflow 3.2.2, not an execution test of Airflow built from `main`. I’m preparing a focused chart fix with regression tests and will open a PR shortly. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
