Deployments provide powerful automation for application management in Kubernetes. One of the things deployments can do is to allow you to perform rolling updates. Rolling updates enable you to update your containers to new versions gradually, without incurring downtime. In this lab, you will have a chance to learn, hands-on, how to perform a rolling update, as well as a rollback to previous version.
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Perform a rolling update of the container version
Update the deployment to the new version like so:
kubectl set image deployment/candy-deployment candy-ws=linuxacademycontent/candy-service:3 --recordCheck the progress of the rolling update:
kubectl rollout status deployment/candy-deploymentIf the update is not finished after a few minutes, something may be wrong with the update.
- Roll back to the previous working state
In this scenario, the rolling update should fail. This is because the specified image,
linuxacademycontent/candy-service:3, does not exist. Roll back to the previous version to get things working again.Get a list of previous revisions.
kubectl rollout history deployment/candy-deploymentUndo the last revision.
kubectl rollout undo deployment/candy-deploymentCheck the status of the rollout.
kubectl rollout status deployment/candy-deploymentThis command should complete soon, saying the rollout was successful.
