Revisions: Every Change Is Versioned
Why each install and upgrade bumps a revision number.
Revisions: Every Change Is Versioned 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.
What a Revision Is
Every time you change a release, Helm records a revision: a numbered snapshot of that release's chart and values at that moment. 🕒
Install Starts at One
A fresh helm install creates revision 1. It is the first entry in the release's history.
Upgrades Bump the Number
Each helm upgrade increments the revision: 1 becomes 2, then 3. The number only ever goes up as you make changes.
helm upgrade my-web ./mychartViewing the History
Run helm history with a release name to see every revision, its status, and what action created it.
helm history my-webWhat History Shows
The history table lists each revision number, the update time, the status, and the chart version that was applied.
REVISION STATUS CHART
1 superseded mychart-0.1.0
2 deployed mychart-0.2.0Snapshots Are Kept
Helm stores each revision's full data in the cluster, so old snapshots stay available for inspection or recovery.
Rolling Back
Because revisions are saved, helm rollback can return a release to any earlier revision in seconds.
helm rollback my-web 1Rollback Adds a Revision
A rollback does not erase history. It applies the old config but records a new revision on top, keeping the timeline intact.
The deployed Status
Only one revision is deployed at a time, the current one. Earlier successful revisions are marked superseded.
Trimming Old Revisions
Helm keeps history per release. The --history-max flag on upgrade caps how many revisions are retained, defaulting to ten.
helm upgrade my-web ./mychart --history-max 5Why Versioning Helps
Numbered revisions give you a safety net: see exactly what changed and undo a bad upgrade without guesswork. 🎯
Quick Check
Let us check how revisions behave.
Recap
Every install, upgrade, and rollback bumps a revision. Helm history lists them, and rollback uses them to recover fast. ✅
Frequently asked questions
Is the “Revisions: Every Change Is Versioned” lesson free?
Yes — the full text of “Revisions: Every Change Is Versioned” 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 “Revisions: Every Change Is Versioned”?
Why each install and upgrade bumps a revision number. 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 “Revisions: Every Change Is Versioned” 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.
All lessons in this course
- What Lives Inside a Chart Package
- A Release Is an Installed Chart
- Revisions: Every Change Is Versioned
- One Chart, Many Releases