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.
This is a Pro chapter
Sign in, then upgrade to Pro or Power to unlock this and the full DevOps Mastery library.
VirtualService configured with 10% canary weight but Prometheus shows 50% of traffic hitting the canary