I’m trying to set up a scenario where I have a single istio ingress gateway that routes to different pieces of my application. For example to access my GraphQL API I could use
<gateway_url>/graphql and for my internal dashboard I could use
The problem I’m having is that when I add a virtual service with a routing rule like this
http: - match: - uri: prefix: /graphql route: - destination: host: my-graphql-api port: number: 80 subset: v1
it routes to
<my-graphql-api>/graphql rather than
<my-graphql-api>/which would mean I’d have to go edit my service source code to nest all routes under
Am I doing this incorrectly or is this the expected behavior? I’ve created these types of reverse proxies with nginx before but I’m having trouble getting the same type of behavior with istio gateway.