Traffic splitting distributes requests among multiple versions of a microservice according to configured percentages or rules. Istio and Anthos Service Mesh apply these controls through the service mesh, without changes to application code. section 4.3.2 section 4.2
Use traffic splitting to manage service changes operationally:
- Redirect a small, controlled share of requests to a new version, validate its behavior, and progressively increase its traffic. section 4.5.3
- Keep old and new versions active simultaneously when rules require different users or cases to reach different implementations. section 4.5.3
- Support A/B testing, canary deployments, progressive rollouts, bug fixes, and releases without downtime. section 4.5.3 section 4.6
Progressive fix rollout
After deploying an urgent fix, route a small percentage of incoming requests to the new version. Verify that the fix works, increase its share, and eventually direct all traffic to it; retain both versions when only selected cases need the fix. section 4.5.3
Table 4.1 Istio traffic management features (view table figure)
Compare traffic splitting with related Istio controls for ingress, egress, request routing, and fault injection. section 4.3.2

