Checks
Motivation
The Kubernetes ecosystem is transitioning from the legacy Ingress resource toward the Gateway API, and many environments—including ours—must migrate away from the nginx-ingress controller, which will be retired at the end of March.
The current Airflow Helm chart only supports Ingress objects, which prevents Airflow from being deployed cleanly in Gateway-only clusters or environments where Ingress controllers are deprecated or no longer available.
We want to continue using the chart without maintaining an additional ingress controller purely for Airflow. Adding
Gateway API / HTTPRoute support would ensure the chart remains compatible with modern Kubernetes networking and aligns with where the community is moving.
This request is not about a specific technical implementation but rather about enabling Airflow users to adopt Gateway API natively through the chart, just as we can today with Ingress.
Implementation
A possible implementation could include:
- Introducing a new httpRoute section in values.yaml, similar in structure to ingress, supporting:
- Parent Gateway references
- Hostnames
- Rules, matches, filters, and backend references for the Airflow webserver and API
- Allowing users to enable either ingress or httpRoute (or both) depending on their environment
- Generating HTTPRoute resources via Helm templates when enabled
This would mirror existing Ingress configuration while aligning it with the Gateway API resource model.
I’m happy to help discuss values structure or contribute feedback, even if I don’t have a full implementation ready.
Are you willing & able to help?
Checks
User-Community Airflow Helm Chart.Motivation
The Kubernetes ecosystem is transitioning from the legacy Ingress resource toward the Gateway API, and many environments—including ours—must migrate away from the nginx-ingress controller, which will be retired at the end of March.
The current Airflow Helm chart only supports Ingress objects, which prevents Airflow from being deployed cleanly in Gateway-only clusters or environments where Ingress controllers are deprecated or no longer available.
We want to continue using the chart without maintaining an additional ingress controller purely for Airflow. Adding
Gateway API / HTTPRoute support would ensure the chart remains compatible with modern Kubernetes networking and aligns with where the community is moving.
This request is not about a specific technical implementation but rather about enabling Airflow users to adopt Gateway API natively through the chart, just as we can today with Ingress.
Implementation
A possible implementation could include:
This would mirror existing Ingress configuration while aligning it with the Gateway API resource model.
I’m happy to help discuss values structure or contribute feedback, even if I don’t have a full implementation ready.
Are you willing & able to help?