Rollback and Recovery

Every environment retains the prior known-good image reference. Rollback selects an immutable tag or digest rather than rebuilding old source.

A rollback decision considers database and configuration compatibility. Forward-only migrations require a tested recovery strategy before release. Argo CD rollback or Git revert restores desired state; emergency manual changes are immediately documented and reconciled.

After recovery, teams preserve logs and evidence, identify the triggering change, add a regression test where feasible, and review whether a gate or observability signal should improve.