Challenge, Easy,  on  Kubernetes

Rolling Update and Rollback a Deployment

Scenario

A Deployment named web-app is running in the production namespace with the image nginx:alpine. You need to update it to a new image using a controlled rolling update strategy, then roll back to the previous version and record the rollout history.

Task

A Deployment named web-app already exists in the production namespace. Update the image to httpd:trixie and configure the rolling update strategy with maxUnavailable: 1 and maxSurge: 1.

Once the rollout completes, roll back the Deployment to the previous revision and confirm the Pods are running nginx:alpine again.

Finally, check the rollout history to find which revision contains httpd:trixie, then save that revision's history output to:

/home/laborant/revision-history-httpd.txt
Hint 1

Use kubectl set image to update the image, kubectl patch to configure the rolling update strategy, and kubectl rollout undo to roll back. To find the revision containing httpd:trixie, use kubectl rollout history with --revision=<number>.

See the official docs: Deployment Rolling Update

Test Cases

How to Author Challenges on iximiuz Labs

Instead of providing a subpar online editing experience, iximiuz Labs offers a helper CLI tool called labctl, allowing you to use your favorite text editor (or a full-featured IDE) to write content from the comfort of your local machine.

Install labctl CLI

curl -sf https://labs.iximiuz.com/cli/install.sh | sh

This will download and install the latest version of the labctl CLI. You only need to do this once per workstation.

Authorize labctl

labctl auth login

This will open a browser window asking you to authorize labctl to access your account. You need to do it after a fresh install of labctl and repeat it whenever the auth session expires.

Pull challenge content

labctl content pull challenge rolling-update-and-rollback-a-deployment-cf48f5ed

This will create a local copy of the challenge content in a directory named rolling-update-and-rollback-a-deployment-cf48f5ed. You only need to do this once per challenge.

Stream your changes

labctl content push -fw challenge rolling-update-and-rollback-a-deployment-cf48f5ed

Run this command in a separate terminal to continuously upload your changes to the server while editing the challenge in your favorite text editor or IDE.

You can also use labctl to create, list, and delete your content. Learn more about the available commands: labctl content --help

Start challenge