Description
Currently, the official Apache Airflow Helm chart only supports the standard Kubernetes Ingress API. Many modern Kubernetes environments are migrating to the Kubernetes Gateway API.
I would like the Helm chart to include optional templates for Gateway API resources, specifically:
HTTPRoute: Support for routing traffic to the Webserver, Flower, and API Server.
Configuration Values: New sections in values.yaml (e.g., gateway.enabled, gateway.web.hostnames, gateway.web.parentRefs) similar to the existing ingress configuration.
The Gateway API is now GA and is becoming the standard for networking in Kubernetes 1.24+.
Use case/motivation
No response
Related issues
The only related discussion I have found: #51967
Are you willing to submit a PR?
Code of Conduct
Description
Currently, the official Apache Airflow Helm chart only supports the standard Kubernetes Ingress API. Many modern Kubernetes environments are migrating to the Kubernetes Gateway API.
I would like the Helm chart to include optional templates for Gateway API resources, specifically:
HTTPRoute: Support for routing traffic to the Webserver, Flower, and API Server.
Configuration Values: New sections in values.yaml (e.g., gateway.enabled, gateway.web.hostnames, gateway.web.parentRefs) similar to the existing ingress configuration.
The Gateway API is now GA and is becoming the standard for networking in Kubernetes 1.24+.
Use case/motivation
No response
Related issues
The only related discussion I have found: #51967
Are you willing to submit a PR?
Code of Conduct