Domain 4.3: Managing Cloud Run resources

You have deployed a new revision of a Cloud Run service. You want to route 10% of the traffic to the new revision for testing, while keeping 90% on the old revision. How can you achieve this?

You have deployed a new version (v2) of your application to Cloud Run. You want to test this new version with a small subset of users before fully rolling it out. You want 10% of traffic to go to v2, and 90% to remain on v1. How should you configure this?

You have deployed a new revision of a Cloud Run service. You want to perform a canary deployment by routing 10% of the incoming traffic to the new revision and keeping 90% on the old revision. How should you configure this?

You have a Cloud Run service currently serving 100% of production traffic. You deploy a new revision of the service, but you only want 10% of user traffic to be routed to the new revision for canary testing. How should you configure this?

You have deployed a new revision of a Cloud Run service. You want to perform a canary deployment by routing exactly 10% of incoming traffic to the new revision, while keeping 90% of traffic on the old revision. How should you configure this?

You have deployed version 1 (v1) of an application to Cloud Run. You just deployed version 2 (v2) and want to perform a canary release. You want 10% of user traffic to go to v2, while 90% remains on v1. How should you configure this in Cloud Run?

You have a Cloud Run service named 'payment-api'. You just deployed a new revision of the service, but you only want 10% of the incoming traffic to be routed to the new revision for testing, while 90% remains on the old revision. Which command should you use to configure this?