How do you rollback a deployment to the previous revision in OpenShift?

• A. Use oc patch to revert to the previous revision.
• B. Use oc rollout undo <resource>/<name> to revert to the previous revision.
• C. Use oc patch to reset to the previous revision.
• D. Delete the deployment and re-create from history.

Answer: (B)

OpenShift keeps a revision history for deployments, and there is a built-in command to revert to a previous revision. Rolling back to the immediately prior revision is done with the rollout undo command for the resource, using the syntax oc rollout undo /. This tells OpenShift to reapply the configuration from the previous revision and trigger a new rollout to bring the system back to that state, including restoring the old pod template and associated ReplicaSet.

This approach is preferred over patching or manually resetting, because patching doesn’t guarantee you’re restoring the exact prior state and would require you to manually recreate the previous spec, risking missed fields. Deleting the deployment would remove the object and its revision history, preventing a clean rollback. If you ever need to revert to a specific older revision rather than just the previous one, you can add --to-revision N to the same command. You can also inspect available revisions with oc rollout history /.