istio-traffic-management

Create a VirtualService with weighted route destinations splitting traffic between stable and canary subsets, such as 90/10. Define the subsets in a DestinationRule using version labels, then gradually shift weight as the canary proves healthy.

Define outlierDetection in a DestinationRule trafficPolicy, setting consecutive5xxErrors, interval, baseEjectionTime, and maxEjectionPercent. Combine it with connectionPool limits on TCP connections and HTTP pending requests to cap load on failing hosts.

A VirtualService defines how traffic is routed to destinations, including matches, weights, retries, and timeouts. A DestinationRule defines policies applied after routing, such as subsets, load balancing, connection pools, and outlier detection.

Yes, Istio supports session affinity through consistentHash load balancing in a DestinationRule. You can hash on an HTTP header, cookie, source IP, or query parameter to route repeat requests to the same backend pod.

Excessive retry attempts amplify load on already struggling backends, worsening outages. Limit attempts, set perTryTimeout, restrict retryOn conditions, and pair retries with outlier detection so unhealthy endpoints are ejected quickly.

Run istioctl analyze to validate configuration, then use istioctl proxy-config routes and endpoints on a deployment to inspect the effective Envoy configuration. Raise proxy log levels with istioctl proxy-config log for deeper traffic debugging.