Release History and Status
What You'll Learn
You'll learn how to track every revision of a deployed Helm release and check its current deployment status using helm history and helm status.
Understanding Release History and Status
When you install or upgrade a Helm release, Helm creates a revision — a snapshot of that deployment. Think of revisions like save points in a video game: each upgrade creates a new save point, and you can always look back to see what happened or even revert to an earlier state.
Viewing Release History
The helm history command shows all revisions for a named release:
helm history my-app
This displays a table with:
- Revision number (1, 2, 3...)
- Updated timestamp
- Status (deployed, superseded, failed)
- Chart version
- Description of what changed
Example output:
REVISION UPDATED STATUS CHART DESCRIPTION
1 Mon Jan 15 10:00:00 2024 superseded my-app-1.0.0 Install complete
2 Mon Jan 16 14:30:00 2024 deployed my-app-1.1.0 Upgrade complete
Checking Current Status
The helm status command gives you a live snapshot of a release's current state:
helm status my-app
This shows:
- Current revision number
- Last deployment time
- Namespace
- Resources deployed (Pods, Services, etc.)
- Status of those resources
Use this when troubleshooting: "Is my app actually running? What resources were created?"
Key Takeaway: helm history tracks the evolution of your releases over time, while helm status gives you the current health and composition of a specific deployment — essential tools for managing and troubleshooting Helm-based applications.