DEVOPS / A CONCEPT NOTE
Rollbacks
undoing a bad release
Overview · mechanism
pitfall · examples
01 / THE SHORT VERSION
The idea in a few sentences.
The process of reverting a system to its last known stable state. Reverting deployments can be achieved by redeploying the previous build artifact or modifying DNS/routing selectors.
02 / FOLLOW THE MECHANISM
How a deployment rollback flows
Outage detection
alerts fire because error rates spike post-deployment.
Rollback command
deployer triggers rollback, pointing active configuration back to previous stable release tag.
Target Swap
system starts launching stable pods while gracefully terminating broken version pods.
Verification
metrics stabilize back to normal baseline range.
04 / COMMAND NOTES
Read the command, then the result.
Inspect the flags and arguments before trying an example. Snippets can need local setup, replacement values, or resources in your own environment.
revert a Kubernetes deployment rollout immediately
kubectl rollout undo deployment/my-appcreate a new commit that undoes the changes of a broken commit
git revert COMMIT_SHA05 / CHECK YOURSELF
Could you explain Rollbacks to a teammate?
Try it out loud in two sentences: what it is, and the one detail that changes the picture. If you stall, the gap is the part to reread.
Up next in Delivery & operationsSLI / SLO / SLAmeasuring 'is it working?'