A cloud engineer needs to perform a safe canary release of an updated container image for an existing Cloud Run service named `billing-app`. What is the correct sequence of steps to execute this release from start to finish?
- 1Deploy the updated container image as a new revision with the `--no-traffic` flag.
- 2Send test HTTP requests to the dedicated revision URL to verify functionality.
- 3Update service traffic to route 10% of production traffic to the new revision for canary testing.
- 4Update service traffic to direct 100% of live traffic to the new revision.
Cevap
The correct deployment order is to first deploy the container image with the `--no-traffic` flag, second test the revision using its dedicated URL, third split a small percentage of production traffic to the revision for canary testing, and finally shift 100% of live traffic to the new revision.
A standard serverless canary deployment pattern on Cloud Run requires first staging the revision using `--no-traffic`, validating it directly via its unique URL, executing a partial traffic split for canary monitoring, and finally promoting the revision to 100% traffic.
Adım Adım Çözüm
Anahtar Kavram
Cloud Run Revision Deployment & Traffic Splitting Workflow