prakharcode opened a new issue, #61452: URL: https://github.com/apache/airflow/issues/61452
### 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](https://gateway-api.sigs.k8s.io/) (the successor to Ingress) for better traffic management, role-oriented configuration, and vendor neutrality. Users who have moved away from ingress-nginx (or similar) to Gateway API implementations (like Istio, Envoy Gateway, or Cilium) currently have to manually manage HTTPRoute resources separately from the Helm release, which breaks the "single package" deployment model. 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+. Adding this would future-proof the Airflow deployment strategy. ### Use case/motivation _No response_ ### Related issues The only related discussion I have found: https://github.com/apache/airflow/discussions/51967 ### Are you willing to submit a 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]
