pavars opened a new issue, #33880: URL: https://github.com/apache/airflow/issues/33880
### Official Helm Chart version 1.10.0 (latest released) ### Apache Airflow version 2.7.0 ### Kubernetes Version 1.24.15 ### Helm Chart configuration Using ArgoCD to deploy airflow helm chart but it's failing to start DAG-processor container because of missing Volumes ```bash Deployment.apps "airflow-global-dag-processor" is invalid: spec.template.spec.containers[2].volumeMounts[1].name: Not found: "webserver-config" ``` This happens because in helpers template the the name is hardcoded to `webserver-config` https://github.com/apache/airflow/blob/0cb875b7ec1cebb101866581166cd7b97047f941/chart/templates/_helpers.yaml#L495 when instead it should use template for airflow_webserver_config_configmap_name like it is in Volume definition https://github.com/apache/airflow/blob/0cb875b7ec1cebb101866581166cd7b97047f941/chart/templates/dag-processor/dag-processor-deployment.yaml#L230 ```yaml ## Current issue {{- define "airflow_webserver_config_mount" -}} - name: webserver-config mountPath: {{ template "airflow_webserver_config_path" . }} subPath: webserver_config.py readOnly: True {{- end }} ## Fix {{- define "airflow_webserver_config_mount" -}} - name: {{ template "airflow_webserver_config_configmap_name" . }} mountPath: {{ template "airflow_webserver_config_path" . }} subPath: webserver_config.py readOnly: True {{- end }} ``` ### Docker Image customizations _No response_ ### What happened _No response_ ### What you think should happen instead Dag-processor should start up without issues ### How to reproduce Enable Dag-processor and provide a custom webserverConfig: |<configinline>and it will not get mounted properly on dag-processor deployment ### Anything else _No response_ ### Are you willing to submit 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
