Tencent Cloud Mesh
- Release Notes and Announcements
- Announcements
- Getting Started
- Application Configuration
- Traffic Control
- Service HA
- Multi-cluster Disaster Recovery and Multi-active
- Security Reinforcement
- Operation Guide
- Mesh Instance Management
- Service Discovery Management
- Traffic Management
- Observability
- Access Management
- Extended Features
- FAQs
Inappropriate VirtualService Route Matching Order
Last updated: 2023-12-26 15:27:43
When writing a VirtualService routing rule, you may set different URIs under the match field to enable requests to be forwarded to different backend services. Sometimes there may be a naming conflict. As a result, only the previous service is always matched. For example:
apiVersion: networking.istio.io/v1beta1kind: VirtualServicemetadata:name: testspec:gateways:- default/example-gwhosts:- 'test.example.com'http:- match:- uri:prefix: /usrvrewrite:uri: /route:- destination:host: usrv.default.svc.cluster.localport:number: 80- match:- uri:prefix: /usrv-expandrewrite:uri: /route:- destination:host: usrv-expand.default.svc.cluster.localport:number: 80
Istio performs matching based on the configuration order, whereas nginx uses longest prefix matching. In this example, prefixes are used for matching. The first prefix is
/usrv, which indicates that the request will be forwarded to the first service as long as the access URI prefix contains /usrv. Because the second matching URI /usrv-expand is also a prefix containing /usrv, the request will never be forwarded to the service matching the second URI.Solution
Adjust the matching order. If the prefixes have a containment relationship, the longer prefix should be placed earlier.
apiVersion: networking.istio.io/v1beta1kind: VirtualServicemetadata:name: testspec:gateways:- default/example-gwhosts:- 'test.example.com'http:- match:- uri:prefix: /usrv-expandrewrite:uri: /route:- destination:host: usrv-expand.default.svc.cluster.localport:number: 80- match:- uri:prefix: /usrvrewrite:uri: /route:- destination:host: usrv.default.svc.cluster.localport:number: 80
Alternatively, the regular matching can be used.
apiVersion: networking.istio.io/v1beta1kind: VirtualServicemetadata:name: testspec:gateways:- default/gatewayhosts:- 'test.example.com'http:- match:- uri:regex: "/usrv(/.*)?"rewrite:uri: /route:- destination:host: nginx.default.svc.cluster.localport:number: 80subset: v1- match:- uri:regex: "/usrv-expand(/.*)?"rewrite:uri: /route:- destination:host: nginx.default.svc.cluster.localport:number: 80subset: v2
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No