Keeping History with --keep-history
Preserving revision records after uninstall.
Keeping History with --keep-history is a free DevOps Bootcamp lesson on CoddyKit. This is lesson 4 of 4. Any 3 lessons of this learning path are free to read in full — after that, CoddyKit PRO unlocks every lesson, plus hands-on practice with a built-in code editor and a 24/7 AI tutor. It is part of the DevOps Bootcamp learning path, and your progress syncs across the web and the CoddyKit app. The DevOps Bootcamp course includes 4 lessons in total.
Why Keep History
Sometimes you want to remove a release but keep its records, so you can roll back later. That is what --keep-history is for. 📜
Add It to uninstall
You pass --keep-history as a flag on helm uninstall to preserve the release's revision records.
helm uninstall my-nginx --keep-historyResources Still Go Away
The Kubernetes objects are still deleted. Only the history of revisions is kept in Helm's storage.
A Lingering uninstalled State
The release now shows the uninstalled status instead of disappearing entirely from Helm's records.
See It with --all
A plain helm list hides it, but helm list --all reveals the uninstalled release still on record.
helm list --allInspect the Saved History
Run helm history on the release name to see the revisions that were preserved by keep-history.
helm history my-nginxRoll Back to Restore
Because the records remain, helm rollback can bring the release back from a kept revision.
helm rollback my-nginx 1The Name Stays Reserved
While history is kept, that release name is taken. A fresh helm install with the same name will conflict.
Fully Remove Later
To finally clear the kept records, run helm uninstall again without the flag to drop the history for good.
helm uninstall my-nginxWhen to Reach for It
Use --keep-history when retiring something you might need to restore, like before a risky migration. 🛟
Default Is Forget
Remember, without the flag uninstall deletes history. --keep-history is the deliberate choice to remember.
Quick Check
Let us confirm what keep-history actually preserves.
Recap
--keep-history removes resources but saves revisions; the release shows as uninstalled and can be rolled back or fully removed later. ✅
Learn DevOps Bootcamp with an AI tutor — free
Write and run real code in your browser, get instant help from a 24/7 AI tutor, and pick up where you left off on the web or in the app.
- Courses
- 142
- Lessons
- 568
Frequently Asked Questions
Is the “Keeping History with --keep-history” lesson free?
Yes — any 3 lessons of the DevOps Bootcamp learning path, including “Keeping History with --keep-history”, are free to read in full here on the web. After that, CoddyKit PRO unlocks every lesson, plus interactive practice with a built-in code editor and a 24/7 AI tutor. The DevOps Bootcamp course includes 4 lessons in total.
What will I learn in “Keeping History with --keep-history”?
Preserving revision records after uninstall. You practise DevOps Bootcamp 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 DevOps Bootcamp?
No prior experience is required. DevOps Bootcamp on CoddyKit is structured for beginners through advanced learners, so you can start here or from the beginning and move at your own pace. This is lesson 4 of 4.
How long does the “Keeping History with --keep-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 DevOps Bootcamp lesson?
Yes. Every DevOps Bootcamp 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
- See Everything with helm list
- Reading helm status Output
- Clean Removal with helm uninstall
- Keeping History with --keep-history