VirtualServiceIneffectiveMatch

    You will receive this message:

    2. kind: VirtualService
    3. metadata:
    4.   name: tls-routing
    5. spec:
    6.   - www1.googleapis.com
    7.   - api1.facebook.com
    9.   - match:
    10.     - port: 2443
    11.       sniHosts:
    12.       - www1.googleapis.com
    13.     - destination:
    14.         host: www1.googleapis.com
    16.     - port: 2443
    17.       sniHosts:
    18.       - www1.googleapis.com
    19.     route:
    20.         host: api1.facebook.com

    In this example, the virtual service specifies two different destinations for the same match. Istio will use the first match, and never send traffic to the second destination.

    How to resolve

    Re-order your routes so that the most specific ones are first. Place ‘catch all’ routes at the end.