michalziobro opened a new issue, #59092:
URL: https://github.com/apache/airflow/issues/59092
### Official Helm Chart version
1.18.0 (latest released)
### Apache Airflow version
any
### Kubernetes Version
1.32
### Helm Chart configuration
```
extraEnvFrom: |
- configMapRef:
name: airflow-cm
```
### Docker Image customizations
_No response_
### What happened
Configuring `extraEnvFrom` in helm values.yaml renders incorrect
pod_template.yaml and makes it impossible to start worker pods (using
KubernetesExecutor).
### What you think should happen instead
Valid pod template should be rendered
### How to reproduce
set:
```
extraEnvFrom: |
- configMapRef:
name: airflow-cm
```
and examine rendered pod_template.yaml:
```
apiVersion: v1
kind: Pod
metadata:
name: placeholder-name
labels:
tier: airflow
component: worker
release: airflow
annotations:
cluster-autoscaler.kubernetes.io/safe-to-evict: "false"
spec:
initContainers:
containers:
- envFrom:
- configMapRef:
name: airflow-cm
env:
- name: AIRFLOW__CORE__EXECUTOR
value: "KubernetesExecutor"
...
```
### Anything else
I think it's quite easy, just remove `-`
[here](https://github.com/apache/airflow/blob/48ae6af196270e51ee9e9af853cacf474633c60b/chart/files/pod-template-file.kubernetes-helm-yaml#L95).
### 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]
