harness to support gateway api for traffic splitting
long-term
J
Jade Puma
Harness currently supports traffic splitting for Istio when using the sidecar data‑plane mode by configuring Istio VirtualServices with weighted routing rules.
Istio now also supports the Kubernetes Gateway API, where traffic routing is defined through HTTPRoute resources and enforced at waypoints in Ambient Mesh. The legacy Istio custom CRDs (e.g., VirtualService, DestinationRule) are now in a frozen status, with no new feature development planned, as the Gateway API has become the standard configuration model.
We require Harness to Full support for Gateway API–based traffic management, alongside continued compatibility with the older, now‑frozen Istio CRDs.
Log In
N
Nautical blue Hedgehog
My Organization is also under going the transition to use Gateway API for traffic routing. This implementation in the Vendor based charts would greatly benefit how we deploy Harness.
Akshit Madan
updated the status to
long-term