Does your rollback restore the last working version?

You've never rolled back a real deploy. You assume the button works.

IntermediateRead 4 minDoing: an afternoon6 steps

What you'll have at the end

A rollback you've run once on purpose, with the exact command written down and the previous version confirmed live afterward

Before you start

You need

A backend service already running as a Kubernetes Deployment with more than one replica, deployed through a real pipeline at least once, with a build step you can still add one line to.

Not covered

Deciding whether to roll back or roll forward once something breaks; this only proves that when you do reach for rollback, it restores the exact build you think it does.

Leans on

6 steps

Where to go next

Add a schema change that both old and new code can use

if the release you're rolling back also shipped a database change, this recipe covers whether the old code can still run safely against the new schema, which the version check alone won't tell you.

Checked 20 Aug 2026

Part of the Backend Deployment cookbook