07 · PackagingLab 42 / 59
Challengehelm
Helm Upgrades, Rollbacks & Release Strategy — Challenge
Ship a release, break the next one on purpose, and get back to a working state in seconds.
- Time
- 22 min
- Level
- Intermediate
- Objectives
- 4 objectives
- Cost
- Free
Where this fits in the platform
This lab adds
- An upgrade you can undo in seconds
Which lets you
—
Before you start
You will need
- Helm 3.14+
- kind or minikube
You do not need these already — the lab environment below provides them.
You will be able to
- Upgrade with `--atomic` so a failed release rolls itself back
- Inspect release history and roll back to a known-good revision
- See what an upgrade would change before running it
The goal#
Achieve the same outcome as Helm Upgrades, Rollbacks & Release Strategy, from an empty starting point, without the steps.
The chart lab taught you to build a chart. This is the other 95% of the job: upgrading it, discovering the new version does not start, and getting back to the one that did — under time pressure.
Hands-on environment
Run this lab in a real terminal, free and in your browser. The environment is temporary and yours alone — break it as much as you like.
Start the challengeOpens in Killercoda, in a new tab — keep this page open for the steps.
This is the guided lab's environment — the same machine, with its walkthrough on the left. Work from the task above and leave those steps alone until you are done, or you are reading the answers.
Run it on your own machine
Run this lab on your own machine. One command starts the environment, with everything the lab needs already installed:
You will need:
- docker
- kubectl
- kind
- helm
git clone https://github.com/EgyKode/EgyKode-lab.git
cd EgyKode-lab
./egykode start k8s
./egykode shellYou need Docker and Git installed. Everything else runs inside the environment. The first start downloads it and takes a few minutes; later starts are seconds.
Not sure what you already have? Run: npm run doctor — it checks and changes nothing.
Anything you tick here is your own record. EgyKode cannot see inside that terminal, so the success criteria stay self-assessed even when the environment checks your work for you.
What must be true when you are done
Step 1 of 3
What must be true when you are done#
- Three revisions exist and
helm historyshows their status. - A deliberately broken upgrade does not leave the release broken.
- You rolled back to a specific revision and verified the running image.
- You can explain what
--atomicdoes that--waitalone does not.
Rules#
- Do not open the guided lab until you are finished, or until the same problem has held you up for 20 minutes.
- Documentation is allowed and encouraged.
- Verify every criterion with a command whose output you can read.
If you get stuck#
- What did you expect, exactly?
- What happened instead — the error text, not a paraphrase?
- Which layer is that error from?
- What is the smallest command that proves the layer below is fine?
You are done when
0 of 4
The concept behind it
Next up
Lab 42 of 59 on the project path