Is there a way in Istio where the subpaths accessed by the application can be specified using a wildcard entry? For ex, in nginx-ingress, this sub route rewrite is handled by mentioning the path as path: /something(/|$)(.*)
We have configured a VirtualService which rewrites https://IP/route to https://IP/. The app further calls others APIs to render the dashboardds etc. These APIs run at /topology
or /api
etc paths. We might not be having the knowledge of the sub-paths that many of the apps use. In this case, is there a way in which any wildcards can be specified (similar to nginx ingress) so that we do not have to worry on the app specific routing and Istio can handle the rest of the sub paths?
Did you get any way to do this ?
We used the below VirtualService
to have a similar functionality. Although this works for most of the cases, it depends on the tool used too, same as nginx-ingress.
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
name: my-vs
spec:
hosts:
- "*"
gateways:
- istio-system/mastergateway
http:
- match:
- uri:
prefix: /something
rewrite:
uri: "/"
route:
- destination:
host: my-service.ethan.svc.cluster.local
port:
number: 80