stephen-bracken opened a new issue, #62358:
URL: https://github.com/apache/airflow/issues/62358
### Official Helm Chart version
1.19.0 (latest released)
### Apache Airflow version
3.1.7
### Kubernetes Version
1.33.5
### Helm Chart configuration
```
mysettings:
hostname: myairflow.example.com
ingress:
apiServer:
enabled: true
hosts:
- "{{ tpl .Values.mysettings.hostname . }}"
tls:
enabled: true
```
### Docker Image customizations
_No response_
### What happened
templating the `hosts` field using `tpl` works for non TLS hosts, but for
the `spec.tls.[*].hosts` section, the
[field](https://github.com/apache/airflow/blob/main/chart/templates/api-server/api-server-ingress.yaml#L58)
is escaped using `{{ .name | quote }}` in the ingress template. This results
in the following:
```
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
annotations: {}
labels:
app: archops-airflow
chart: airflow-1.19.0
component: airflow-ingress
heritage: Helm
release: archops-airflow
tier: airflow
name: airflow-ingress
spec:
rules:
- host: myairflow.example.com
http:
paths:
- backend:
service:
name: airflow-api-server
port:
name: api-server
path: /
pathType: ImplementationSpecific
tls:
- hosts:
- '{{ tpl .Values.mysettings.hostname . }}'
secretName: null
```
### What you think should happen instead
The `spec.tls.[*].hosts` fields need to be templated in the same way as the
`spec.rules.[*].hosts` field.
### How to reproduce
see Helm chart configuration
### Anything else
_No response_
### 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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
