Answer-first summary for fast verification
Answer: Deploy the feature with “Serve this revision immediately” unchecked, and configure the new revision to serve a small percentage of traffic. Check for errors, and increase traffic to the revision as appropriate.
Option C is the correct choice because it directly leverages Cloud Run's built-in capability for gradual traffic shifting between revisions. This approach allows for deploying a new revision without immediately serving all traffic to it, enabling a controlled and monitored rollout. By starting with a small percentage of traffic and gradually increasing it after verifying the new revision's stability, you adhere to the SRE team's mandate for gradual deployments with minimal manual intervention. Options A and B involve more complex configurations or code changes that are unnecessary given Cloud Run's native features. Option D contradicts the requirement for gradual deployment by serving the new revision immediately, which could lead to significant downtime if issues arise.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
How can you implement a gradual deployment for a new feature on Cloud Run with minimal effort, adhering to your company's SRE team's requirement to avoid large downtimes from code changes?
A
Configure the application’s frontend load balancer to toggle between the new and old revisions.
B
Configure the application code to send a small percentage of users to the newly deployed revision.
C
Deploy the feature with “Serve this revision immediately” unchecked, and configure the new revision to serve a small percentage of traffic. Check for errors, and increase traffic to the revision as appropriate.
D
Deploy the feature with “Serve this revision immediately” checked. Check for errors, roll back to the previous revision, and repeat the process until you have verified that the deployment is bug-free.
No comments yet.