helm status: Usage, Options & Common CI Errors

Inspect a single release: state, resources, and notes.

helm status reports the current condition of one release - its deployment status, the resources it owns, and the rendered NOTES.txt. It is the targeted view that complements the list overview.

What it does

helm status NAME prints the release's status (deployed, failed, pending-upgrade, etc.), last-deployed time, and notes. --show-resources lists the Kubernetes objects in the release with their state; --revision inspects a specific past revision. It errors if the release does not exist, which makes it a clean existence check.

Common usage

Terminal

helm status web -n prod
helm status web --show-resources
helm status web --revision 3
helm status web -o json

Common errors in CI

A status of pending-install or pending-upgrade that never clears means a prior helm command was interrupted (CI cancelled mid-deploy) - the release is stuck and the next upgrade reports "another operation (install/upgrade/rollback) is in progress". helm status surfaces that state so you can intervene (roll back or, as a last resort, clear the pending state). "Error: release: not found" is a definitive "this release does not exist here", more reliable than scraping helm list output for existence in scripts.

Related guides

kubectl Cheat Sheet: Commands for Everyday KubernetesA kubectl cheat sheet - get, describe, logs, apply, rollout, debug, and context commands for daily Kubernetes… helm list: Usage, Options & Common CI Errorshelm list shows releases and their status. All-namespaces, status filters, output formats for scripting, and… Helm Release Stuck in "pending-upgrade" - Recover in CIRecover a Helm release stuck in pending-install/pending-upgrade/pending-rollback in CI - clear the dead in-fl… Helm "another operation (install/upgrade/rollback) is in progress"Fix Helm "another operation (install/upgrade/rollback) is in progress" in CI - a release stuck pending-* afte…