Escaping pending-upgrade and Stuck States
Recovering a release wedged mid-operation.
Escaping pending-upgrade and Stuck States 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.
When a Release Wedges
If an upgrade is interrupted, a release can get stuck in pending-upgrade and refuse every new operation. Do not panic. 🛑
Spotting the State
Run helm list and a stuck release shows a status like pending-upgrade or pending-install instead of the healthy deployed.
helm list --all --namespace webWhy It Happens
A pending status means Helm started writing a revision but never finished, often because a process was killed or a timeout hit mid-upgrade.
The Cleanest Fix
The safest escape is to roll back to the last good revision. helm rollback returns the release to a known, healthy state.
helm rollback my-app 0Picking the Target
Check helm history first to see which revision was last deployed cleanly, then roll back to that exact number.
helm history my-appRollback to Zero
Passing revision 0 is a handy shortcut: it tells Helm to roll back to the previous release without you naming the number.
helm rollback my-appReleases Are Stored as Secrets
Helm 3 keeps each revision in a Kubernetes Secret in the release namespace. That record is what tracks the pending status.
Inspecting the Records
List those Secrets to see the revision history directly. The newest one carries the pending state that is blocking you.
kubectl get secret -l owner=helm,name=my-app -n webThe Last-Resort Cleanup
If rollback cannot help, delete the failed pending revision Secret. Helm then falls back to the prior revision as the latest.
kubectl delete secret sh.helm.release.v1.my-app.v5 -n webThen Retry the Upgrade
Once the stuck record is cleared, run your helm upgrade again. With a clean state, it proceeds normally this time.
helm upgrade my-app ./my-appPrevent It Next Time
Adding --atomic to upgrades avoids stuck states entirely: a failed run rolls itself back instead of leaving you wedged.
helm upgrade my-app ./my-app --atomic --timeout 5mQuick Check
A release is stuck in pending-upgrade. What is the safest first action to recover it?
Recap
You now rescue stuck releases: spot pending status, helm rollback to a good revision, or delete the failed release Secret. Use --atomic to prevent it. 🚀
Frequently asked questions
Is the “Escaping pending-upgrade and Stuck States” lesson free?
Yes — the full text of “Escaping pending-upgrade and Stuck States” 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 “Escaping pending-upgrade and Stuck States”?
Recovering a release wedged mid-operation. 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 “Escaping pending-upgrade and Stuck States” 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
- Tracing Renders with --debug and --dry-run
- Reading Manifests with helm get all
- Escaping pending-upgrade and Stuck States
- Build a Production App Chart End to End