Explanation:
The correct answer is D because the image can be directly updated using the kubectl command, and Kubernetes Engine performs a rolling update. This method allows for updating the images, configuration, labels, annotations, and resource limits/requests of the workloads in your clusters without downtime. Rolling updates incrementally replace your resource’s Pods with new ones, which are then scheduled on nodes with available resources.
For example, to update a Deployment from nginx version 1.7.9 to 1.9.1, you would run the following command:
kubectl set image deployment nginx nginx=nginx:1.9.1
kubectl set image deployment nginx nginx=nginx:1.9.1
This command updates the nginx image of the Deployment’s Pods one at a time.
Ultimate access to all questions.
A company is hosting their Echo application on Google Cloud using Google Kubernetes Engine. The application is deployed with deployment echo-deployment exposed with echo-service. They have a new image that needs to be deployed for the application. How can the change be deployed with minimal downtime?
A
Delete the deployment and create a new deployment with the updated image
B
Update image in instance template and use rolling deployment of instance group with Kubernetes engine.
C
Delete the service and create a new service with the updated image
D
Update image using kubectl set image deployment
No comments yet.