INFRA-DEVOPS Contents

Rollback Strategy and Release Safety

Rollback runbooks: when to revert, what signals to watch, and how to make rollbacks fast and boring.

On this page

Rollback Decision Tree

  • New deploy broke prod → rollback immediately (restore service).
  • Data migration involved → prefer forward fix if rollback unsafe.
  • Partial impact → canary abort / traffic shift before full rollback.

Rollback Runbook (Kubernetes Example)

kubectl -n <ns> rollout history deploy/<name>
kubectl -n <ns> rollout undo deploy/<name>
kubectl -n <ns> rollout status deploy/<name> --timeout=5m

Post-Rollback Verification

  • Key endpoints healthy, error rate normal
  • Queues draining, retries stable
  • No crash loops, no new alerts

Failure Modes

  • Rollback without verification → silent partial outage.
  • Rollback blocked by schema mismatch → plan reversibility upfront.