clarify support for VirtualService in waypoints #16670
Conversation
istio-testing
added
the
size/M
craigbox
added
the
cherrypick/release-1.26
| | [`TLSRoute`](https://gateway-api.sigs.k8s.io/guides/tls) | Alpha | `parentRefs` | | ||
| | [`TCPRoute`](https://gateway-api.sigs.k8s.io/guides/tcp/) | Alpha | `parentRefs` | | ||
|
|
||
| (TLS and TCP routing are stable features in Istio, but support for these objects remains at Alpha because the Gateway API objects are still in the experimental channel.) |
There was a problem hiding this comment.
That's tough, so there is no stable way of managing tcp traffic in ambient.
There was a problem hiding this comment.
Yep - and it's really because Gateway API is (rightly) hesitant about pushing those APIs forward without implementations that are championing those use-case.
|
|
||
| Gateway API has no ability to address [subsets](/docs/reference/config/networking/destination-rule/#Subset). Instead, you must define additional Services which have a more granular selector than the original. | ||
|
|
||
| The other features of DestinationRule are supported. |
There was a problem hiding this comment.
exportTo is also not supported, but I think @Stevenjin8's PR covers that?
There was a problem hiding this comment.
Is workloadSelector supported?
If not we could basically say "only trafficPolicy is supported"
There was a problem hiding this comment.
istio/istio#51085 isn't clear, so I'm guessing it does work
|
https://docs.google.com/document/d/1JjsPzOMJfu_evzgiRp-aJf1KDpa9ImyYrew__y5CTao/edit?tab=t.0#heading=h.8vlgwrna7yow for the broader terminology discussion |
Update the ambient docs to clarify that waypoint support for VirtualService is alpha, why that is, and what that means you have to think about during a migration.