Reviewing helm history
Reading the revision log to pick a target.
Reviewing helm history is a free Helm Academy lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Helm Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Releases Remember
Every install and upgrade is recorded. The helm history command shows that timeline for a release, one row per revision. 📜
helm history my-appReading the Columns
The output lists each REVISION with its update time, status, chart, app version, and a short description of what happened.
The Revision Number
The REVISION column is the key: it counts up from 1 and is the exact value you will hand to a rollback later.
The Status Field
The STATUS tells the fate of each revision: deployed, superseded, failed, or pending. Only one revision is deployed at a time.
Superseded Means Replaced
When you upgrade, the old revision becomes superseded. It still lives in history so you can return to it if needed.
Spotting a Failure
A revision marked failed shows an upgrade that did not complete. History makes it obvious which revision was the last good one.
The Description Column
The DESCRIPTION column gives a human note like Upgrade complete or Rollback to 2, so you can scan intent at a glance.
Limit the Output
Long-lived releases pile up revisions. Use --max to show only the most recent few rows instead of the whole list.
helm history my-app --max 5Machine-Readable Output
Need to parse history in a script? Ask for -o json or -o yaml to get structured output instead of the table.
helm history my-app -o jsonMind the Namespace
History is scoped to a namespace. If the release lives elsewhere, pass -n so Helm looks in the right place.
helm history my-app -n webHistory Drives Rollback
Think of helm history as the menu you read before choosing a rollback target. Pick the last known-good revision, then act on it.
Quick Check
You ran an upgrade that broke. In helm history, what is the status of the previous, replaced revision?
Recap
You can now read helm history: revisions, statuses like deployed and superseded, and descriptions. It is the map you use to choose a rollback target. 🧭
Frequently asked questions
Is the “Reviewing helm history” lesson free?
Yes — the full text of “Reviewing helm history” is free to read here on the web, and the Helm Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Helm Academy course, upgrade to CoddyKit PRO.
What will I learn in “Reviewing helm history”?
Reading the revision log to pick a target. You practise Helm Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Helm Academy?
No prior experience is required. Helm Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Reviewing helm history” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Helm Academy lesson?
Yes. Every Helm Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.