You work for an organization that manages an ecommerce site.

https://cloud.google.com/load-balancing/docs/https/traffic-management-global#traffic_actions_weight-based_traffic_splitting

Deploying a new version of an existing production service generally incurs some risk. Even if your tests pass in staging, you probably don't want to subject 100% of your users to the new version immediately. With traffic management, you can define percentage-based traffic splits across multiple backend services.

For example, you can send 95% of the traffic to the previous version of your service and 5% to the new version of your service. After you've validated that the new production version works as expected, you can gradually shift the percentages until 100% of the traffic reaches the new version of your service. Traffic splitting is typically used for deploying new versions, A/B testing, service migration, and similar processes.

https://cloud.google.com/traffic-director/docs/advanced-traffic-management #weight-based_traffic_splitting_for_safer_deployments

https://cloud.google.com/architecture/implementing-deployment-and-testin g-strategies-on-gke#split_the_traffic_2

https://cloud.google.com/load-balancing/docs/https/traffic-management-glob al#traffic_actions_weight-based_traffic_splitting