Explanation:
The question involves selectively rolling back the update for Pods experiencing errors in a specific zone with minimal impact to users. Option A suggests scaling down the Pods in the affected zone and redeploying, which does not address the root cause of the errors and may lead to service disruption. Option B involves draining the affected nodes and redeploying, which is more about node maintenance than addressing deployment issues. Option C is the correct approach as it involves modifying the Deployment to use the previous version's Pod template and performing a rolling update specifically for the affected zone, ensuring minimal impact to users. Option D suggests rolling back the entire deployment, which is not selective and affects all zones, not just the one with issues. Therefore, the correct answer is C.
Ultimate access to all questions.
No comments yet.
You are rolling out a new version of your application to a multi-zone Google Kubernetes Engine (GKE) cluster. The deployment is proceeding as expected, but Pods in one zone are encountering elevated error rates. How can you perform a targeted rollback of the update for only the affected Pods while minimizing user disruption?
A
Scale down the Pods in the affected zone. Redeploy the new version of the application.
B
Drain the affected nodes. Redeploy the new version of the application to the remaining nodes.
C
Modify the Deployment to use the Pod template from the previous version of your application. Perform a rolling update to replace the Pods in the affected zone.
D
Use the kubectl rollout undo command to roll back the entire deployment. Redeploy the new version of the application, excluding the affected zone.