Resending because I sent this before I was subscribed. ---------- Forwarded message --------- From: Matan Romanov <[email protected]> Date: Wed, May 27, 2026 at 3:40 PM Subject: [FEATURE] Add HTTPRoute / Gateway API support to YuniKorn Helm chart To: <[email protected]>
Hi YuniKorn community, I'd like to request a new feature for the YuniKorn Helm chart. The chart currently only supports Ingress for exposing the YuniKorn UI and service. Our organization recently migrated to Envoy Gateway, which uses the Kubernetes Gateway API (HTTPRoute) instead of Ingress. Because the chart has no support for HTTPRoute in values.yaml, we can't manage the route as part of the Helm release and have to apply it manually as a standalone resource outside of the chart lifecycle. We'd love to see an opt-in httpRoute block added to values.yaml so that users on Gateway API implementations (Envoy Gateway, Istio, Contour, etc.) can manage their routing configuration through the chart like everyone else. Is this something the community would consider? Happy to provide more details or context if helpful. Thanks -- Matan Romanov [image: Icon] [email protected] [image: Company logo] <https://similarweb.com> similarweb.com [image: Linkedin Icon] <https://www.linkedin.com/company/similarweb/> [image: X Icon] <https://x.com/Similarweb> [image: Instagram Icon] <https://www.instagram.com/similarwebinsights?igsh=cWRzNThoZzc2cXEz> [image: Facebook Icon] <https://www.facebook.com/Similarweb> [image: Banner] <https://www.similarweb.com> [image: __tpx__] -- Matan Romanov [image: Icon] [email protected] [image: Company logo] <https://similarweb.com> similarweb.com [image: Linkedin Icon] <https://www.linkedin.com/company/similarweb/> [image: X Icon] <https://x.com/Similarweb> [image: Instagram Icon] <https://www.instagram.com/similarwebinsights?igsh=cWRzNThoZzc2cXEz> [image: Facebook Icon] <https://www.facebook.com/Similarweb> [image: Banner] <https://www.similarweb.com> [image: __tpx__]
