[
https://issues.apache.org/jira/browse/YUNIKORN-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg resolved YUNIKORN-3287.
---------------------------------------------
Fix Version/s: 1.10.0
Resolution: Fixed
Change committed to master for 1.10 release
> 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
> Assignee: weichen lai
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]