Reverting with helm rollback
Returning to a known-good revision in seconds.
Reverting with helm rollback is a free Helm Academy lesson on CoddyKit — lesson 4 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.
When Things Go Wrong
A bad upgrade happens to everyone. Because Helm keeps history, you can undo it with helm rollback instead of debugging under pressure. 🛟
Roll Back One Step
Called with just the release name, helm rollback returns to the immediately previous revision. The fastest way to undo a fresh mistake.
helm rollback my-appTarget a Specific Revision
You can also name the exact revision to restore. Read it from helm history, then pass that number.
helm rollback my-app 3Rollback Is Itself a Revision
A rollback does not erase history. It creates a brand-new revision whose contents match the target you chose. History only grows.
Restores Values Too
Rollback restores the chart and the values from the target revision together, so the release returns to that exact configuration.
Wait for It to Settle
Add --wait so Helm blocks until the restored pods are ready, confirming the rollback truly recovered the service. ✅
helm rollback my-app 3 --waitPreview the Rollback
Want to see what a rollback would produce first? Add --dry-run to render it without changing the live release.
helm rollback my-app 3 --dry-runRoll Back Hooks Too
By default rollback skips hooks. Add --no-hooks to be explicit, or omit it to let any rollback hooks run as designed.
helm rollback my-app 3 --no-hooksConfirm the New State
After rolling back, run helm status or helm history again to confirm the deployed revision is the one you expected.
helm status my-appAtomic Already Rolls Back
If your failed upgrade used --atomic, Helm already rolled back for you. Manual rollback is for problems found after the fact.
History Must Exist
Rollback needs a stored revision to return to. If history was purged, there is nothing to restore, so history retention is your safety net.
Quick Check
Your release is at revision 6, all good. You run helm rollback my-app 4. What happens to the revision count?
Recap
You can now recover fast with helm rollback: undo one step or target a revision, each rollback a new revision restoring its chart and values. Pair it with history and --atomic. 🚀
Frequently asked questions
Is the “Reverting with helm rollback” lesson free?
Yes — the full text of “Reverting with helm rollback” 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 “Reverting with helm rollback”?
Returning to a known-good revision in seconds. 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 4 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Reverting with helm rollback” 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
- Apply Changes with helm upgrade
- Install-or-Upgrade with --install
- Reviewing helm history
- Reverting with helm rollback