helm status: Command Reference for CI/CD

By Kaveh Alemi·Latchkey

Inspect a release current state, revision, and resources.

helm status reports a release deployment status, its current revision, and the resources it manages. In CI it is the verification read after a deploy and a script-friendly source of the release state. This reference covers its flags.

Common flags and usage

status <release>: show status, revision, and resources
-o json|yaml: machine-readable output for CI assertions
--revision N: show the status of a specific revision
--show-resources: list the managed Kubernetes objects
Pair with helm list to enumerate releases in a namespace

Example

shell

STATE=$(helm status web -n prod -o json | jq -r '.info.status')
[ "$STATE" = "deployed" ] || { echo "release not deployed: $STATE"; exit 1; }

In CI

Assert on helm status -o json after a deploy to confirm the release reached the deployed state rather than failed or pending-upgrade. The JSON output is stable enough to parse with jq, making status the clean verification read at the end of a deploy job.

Using this in CI

A runner has no kubeconfig, no cached context, and no interactive auth. Every kubectl invocation in CI needs the context supplied explicitly, and most confusing CI failures here are the command running against the wrong cluster or no cluster at all.

Terminal

# never rely on the ambient context on a runner
kubectl --context "$KUBE_CONTEXT" -n "$NAMESPACE" get pods

# confirm what you are actually connected to before mutating anything
kubectl config current-context
kubectl cluster-info

# fail fast instead of hanging on an unreachable API server
kubectl --request-timeout=30s get nodes

Key takeaways

status -o json gives a parseable release state for CI assertions.
A healthy release reports status "deployed", not pending or failed.
--show-resources lists exactly what the release manages.

Frequently asked questions

helm status: Command Reference for CI/CD?

In CI?