Skip to content
EgyKode
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

Before you start

You will need

  • Helm 3.14+
  • kind or minikube

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

CostFree

— kind or minikube.

How to clean up

You are done when

0 of 4

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.

What must be true when you are done#

  • Three revisions exist and helm history shows 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 --atomic does that --wait alone 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#

  1. What did you expect, exactly?
  2. What happened instead — the error text, not a paraphrase?
  3. Which layer is that error from?
  4. What is the smallest command that proves the layer below is fine?

The concept behind it

Stuck?Open the guided lab

Next up

Lab 42 of 58 on the project path

Managing EKS Cluster Add-ons with Helm & IRSAInstall the controllers a cluster needs to be useful, each with its own AWS identity instead of node credentials.39 minIntermediateBillable — destroy resources when you finish