You have an application deployed on Kubernetes Engine using a Deployment named echo-deployment. The deployment is exposed using a Service called echoservice.
You need to perform an update to the application with minimal downtime to the application. What should you do?
A. Use kubectl set image deployment/echo-deployment <new-image>
B. Use the rolling update functionality of the Instance Group behind the Kubernetes cluster
C. Update the deployment yaml file with the new container image. Use kubectl delete deployment/echo-deployment and kubectl create -f <yaml-file>
D. Update the service yaml file which the new container image. Use kubectl delete service/echo-service and kubectl create -f <yaml-file>
|
Download Printable PDF. VALID exam to help you PASS. |
 |
a
A
Clearly correct answer is A
command is:
kubectl set image deployment/mydeployment mydeployment=gcr.io/$PROJECT_ID/container-image:v2
B is funny.
There is no rolling update functionality in the **Instance Group behind the Kubernetes cluster**
A
B is correct. https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app
You need to supply the version tag , so A command is incomplete
A is correct
A?
Should be A.
Rolling update in k8s is kubectl command, instance group is backout/rolling for VM services.
For B, I think the instance group implies the node pool of k8s. Rolling update is required for minimal downtime
For A, it is one step for application update. Acutally kubectl is just one method of this step. You can also use Deployment Manager.
So I think B makes more sense.
A. This process is called a rolling update. Secondly, we don’t have to update the instance group. So A
I think it’s B.
The condition is “minimal downtime”
Rolling updates are designed to update your workloads without downtime
Yes Answer should be A. Funny the reference itself says Set Image should be used 🙂
should be A.