Istio
Hard
Traffic Management
You add subset v2 to a DestinationRule and route a VirtualService to it in the same kubectl apply. Some requests fail with 503 for a few seconds. Why?
Select your answer:
Show answer and explanation
Answer: The VirtualService can reach proxies before the subset definition
Explanation
Istio propagates configuration to istiod and the proxies in an eventually consistent way, so one kubectl apply does not guarantee order. If the VirtualService arrives first, Envoy refers to a subset cluster that does not exist yet and returns 503 until the DestinationRule lands. Use make-before-break: add the subset, wait, then update the VirtualService.
More hard Istio questions
- What is the purpose of Istio's WorkloadEntry resource?
- What is the purpose of Istio's WorkloadGroup resource?
- What is the purpose of Istio's 'consistentHash' load balancing in DestinationRule?
- How can you implement rate limiting in Istio?
- What is the purpose of Istio's 'locality' field in DestinationRule?
- What is the purpose of Istio's 'mirror' field in VirtualService?