You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2026/05/29 00:17:00 UTC

[jira] [Updated] (YUNIKORN-3287) Add HTTPRoute / Gateway API support to YuniKorn Helm chart

     [ https://issues.apache.org/jira/browse/YUNIKORN-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wilfred Spiegelenburg updated YUNIKORN-3287:
--------------------------------------------
       Component/s: release
     Fix Version/s:     (was: 1.9.0)
    Target Version: 1.9.0

> Add HTTPRoute / Gateway API support to YuniKorn Helm chart
> ----------------------------------------------------------
>
>                 Key: YUNIKORN-3287
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-3287
>             Project: Apache YuniKorn
>          Issue Type: New Feature
>          Components: release, shim - kubernetes
>            Reporter: Matan Romanov
>            Priority: Major
>
> The YuniKorn Helm chart currently only supports Ingress for exposing the YuniKorn UI and service. Organizations migrating to Envoy Gateway or other Kubernetes Gateway API implementations (Istio, Contour, etc.) cannot configure HTTPRoute resources through values.yaml, forcing them to manage the route as a manual standalone resource outside the chart lifecycle.
> We'd like to request an opt-in httpRoute block added to values.yaml so that users on Gateway API implementations can manage their routing configuration through the chart like everyone else.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org