Walk a 503 After a Subset Change
Debug subset routing failures by checking route, subset definition, and workload labels in order.
Canary failure Header-matched beta traffic to reviews:v3 returns 503. Stable traffic to reviews:v1 is healthy. Subset bugs look like application bugs until you follow the object chain. Route-subset-label chain VirtualService names it; DestinationRule defines it; pods prove it. Subset routing is a three-part contract across mesh and Kubernetes objects. Tail app logs Useful later, weak first. The missing link becomes visible. Follow the routing contract before debugging the application. VS Route DR Subset P Labels First fork The VirtualService match for header x-beta=true sends traffic to host reviews subset v3.
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in