advancedService Mesh: Istio, Envoy & mTLS
VirtualService configured with 10% canary weight but Prometheus shows 50% of traffic hitting the canary
Check that DestinationRule with correct subset labels matches your Pod versions accurately. If subset selectors don't correctly identify which Pods are v1 vs v2, Envoy may not be routing as expected. Also verify the VirtualService is in the same namespace as the service or correctly references it.
Ready to master this question?
Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.
Sign in to generate a response