Replies: 1 comment
-
In my gateway vs, there're hundreds of different url matching rules and route to a bunch of different upstream svcs. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have an istio-gateway to handle sourth-north trafic, and I created a virtualservice for that gateway to make requests with different urls can be routed to different SVCs, something like:
And then, I want to achieve that all the traffic that will be routed to foo.ns.svc.cluster.local can be split by header and then routed to different subsets. Just like doing grayscale publish.
But this didn't work. Traffic in the mesh can go to desired subset, but traffic from outside of the cluster(which go through the gateway) go to random subset.
The reason why I created an individual vs for foo.ns.svc.cluster.local is that I want all the traffic can apply this routing rule no matter where it comes from(outside mesh or inside mesh).
Am I missing something, or how to achieve this?
Beta Was this translation helpful? Give feedback.
All reactions