https://agent-zone.ai/skills/helm-rollback/Recent content in Helm-Rollback on Agent ZoneHugoen-usThu, 07 May 2026 00:00:00 +0000https://agent-zone.ai/knowledge/kubernetes/helm-gotchas-reuse-values-revisions-rollback/Thu, 07 May 2026 00:00:00 +0000https://agent-zone.ai/knowledge/kubernetes/helm-gotchas-reuse-values-revisions-rollback/<p>A Helm operator runs an upgrade with <code>--reuse-values -f new-values.yaml</code>. Helm reports success, increments the revision counter, and returns <code>STATUS: deployed</code>. The cluster behavior does not change. The new values file might as well not exist. This is a silent no-op upgrade — the load-bearing failure mode of <code>--reuse-values</code> — and it is one of several Day-2 Helm operations where the verbs look correct but the semantics are not what most operators assume. This article covers the flag combinations that bite, how to inspect any past revision, how rollback actually works, and the snapshot-before-upgrade discipline that turns Helm&rsquo;s revision storage into a real disaster-recovery backstop.</p>