Cloud Run manages traffic splitting at the revision level within a single service. When you deploy an updated version of your application, Cloud Run creates a new revision of the existing service. You can then use Cloud Run's built-in traffic management to split a specified percentage of traffic between the new revision and the previously running revision, enabling a canary rollout without needing an external load balancer or a separate service. For example, deploy the new revision with gcloud run deploy --no-traffic, then run gcloud run services update-traffic SERVICE --to-revisions NEW_REVISION=10 to send it 10% of the traffic. This is the documented method for performing gradual/canary rollouts on Cloud Run.
Community Discussion