scali opened a new issue, #52632: URL: https://github.com/apache/airflow/issues/52632
### Official Helm Chart version 1.17.0 (latest released) ### Apache Airflow version 3.0.2 ### Kubernetes Version 1.31.8 ### Helm Chart configuration ```yaml apiServer: apiServerConfigConfigMapName: "my-airflow-config" ``` ### Docker Image customizations _No response_ ### What happened If I use custom name for my api server config map : ```sh kubectl create configmap -n airflow my-airflow-config \ --from-file=webserver_config.py=configmap/webserver_config.py ``` and in chart : ```yaml apiServer: apiServerConfigConfigMapName: "my-airflow-config" ``` The deployment fails ### What you think should happen instead We should be able to add custom config map name (e.g. to respect the company naming convention) 💡 It seems to be related to [this line in _helpers.yaml](https://github.com/apache/airflow/blob/main/chart/templates/_helpers.yaml#L597). Should the value of `.Values.webserver.webserverConfigConfigMapName` be replaced by `.Values.apiServer.apiServerConfigConfigMapName` ? ### How to reproduce Create an apiserver confimap with a custom name : ```sh kubectl create configmap -n airflow my-airflow-config \ --from-file=webserver_config.py=configmap/webserver_config.py ``` and add this value to the chart : ```yaml apiServer: apiServerConfig: ~ apiServerConfigConfigMapName: "my-airflow-config" ``` ### Anything else ## Workaround solution It works if I use build-in name (` airflow-api-server-config`) for my api server config map : ```sh kubectl create configmap -n airflow airflow-api-server-config \ --from-file=webserver_config.py=configmap/webserver_config.py ``` ```yaml apiServer: apiServerConfigConfigMapName: "airflow-api-server-config" ``` ### Are you willing to submit PR? - [ ] 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