# 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?

Istio, Hard (Expert), Traffic Management. https://k8wiz.com/uquiz/you-add-subset-v2-to-a-destinationrule-and-route-a-virtualservice-to-it-in-the-same-kubectl-apply-some-requests-fail-with-503-fo

- A. kubectl applies a VirtualService only after the next sidecar restart
- B. New subsets receive no endpoints until outlier detection clears them
- C. The sidecar rejects routes to a subset until istioctl analyze passes
- D. The VirtualService can reach proxies before the subset definition

**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.
