Answer-first summary for fast verification
Answer: Update the service object in Kubernetes to direct traffic back to the stable pods.
Correct: Update the service object in Kubernetes to direct traffic back to the stable pods. In a canary deployment, traffic is managed at the Kubernetes service level. The service object routes traffic to different sets of pods (stable vs canary). To roll back the canary release, you would update the service object to direct traffic away from the canary pods and back to the stable pods. Incorrect: Delete all pods associated with the canary release. This does not guarantee traffic redirection to the stable version and could lead to service disruptions. Incorrect: Use Google Cloud Deployment Manager to switch back to the previous version of the application. Google Cloud Deployment Manager is used for creating and managing cloud resources, not for handling traffic redirection in a canary deployment scenario in GKE. Incorrect: Implement a new canary release with fixes for the errors. This does not constitute a rollback and does not guarantee that the new fixes will resolve the issues.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You're a Cloud DevOps Engineer who has deployed a canary release of a new application on Google Kubernetes Engine (GKE) to test new features. Unexpected errors are causing system disruptions. What's the best action to roll back the experimental canary release?
A
Implement a new canary release with fixes for the errors.
B
Delete all pods associated with the canary release.
C
Update the service object in Kubernetes to direct traffic back to the stable pods.
D
Use Google Cloud Deployment Manager to switch back to the previous version of the application.
No comments yet.