You are building and deploying a microservice on Cloud Run for your organization. Your service is used by many applications internally. You are deploying a new release, and you need to test the new ve

Deploying the new version to a staging environment first allows developers to perform initial, isolated testing. Subsequently, applying a small traffic split (e.g., 1%) to the new version in the production environment enables a canary rollout, allowing for extensive testing with real production traffic while minimizing impact to the majority of users, which is a core Cloud Run feature for safe deployments.

Allowing 50% traffic to a new version is a significant exposure and does not align with minimizing user impact for initial extensive testing in production.

Deploying with a new-release tag *without sending traffic* is useful for internal testing or specific URL access, but it doesn't cover 'extensive testing in the production environment' with live user traffic.

Deploying a new environment with a 'green' tag as a staging environment is a less efficient approach in Cloud Run, which natively supports multiple revisions and traffic splitting within a single service, designed to manage canary deployments or blue/green strategies seamlessly without full environment duplication.