Helm cannot find the release you're trying to upgrade, rollback, or delete. This usually means the release was never installed or was in a different namespace.
Fixes Error: release: not found
helm list -Ahelm list -AError: release: not found
Helm stores release metadata in the cluster (typically in Secrets or ConfigMaps). If a release was not properly installed or was installed in a different namespace, helm list won't show it and operations on it will fail. This is common when managing releases across namespaces.
Check what releases exist:
helm list -ALook for the release name across all namespaces.
If the release is in a different namespace:
helm list -n NAMESPACE
helm status RELEASE_NAME -n NAMESPACEView release revisions:
helm history RELEASE_NAME -n NAMESPACEIf empty, the release wasn't installed via Helm.
If the release doesn't exist, install it:
helm install RELEASE_NAME CHART_NAME -n NAMESPACE --create-namespaceFor CI/CD, use upgrade with --install flag:
helm upgrade --install RELEASE_NAME CHART_NAME -n NAMESPACE --create-namespaceThis installs if not found, upgrades if it exists.
Helm release names are case-sensitive. Always use helm list -A to verify where releases are installed. For GitOps workflows (ArgoCD, Flux), let the operator manage releases instead of manual helm commands. Use helm template locally to test chart rendering before installation. Consider using Helm hooks for pre/post install validation.