A rollback returns a service to a previous known working release. Use the deployment history to choose the target. Check whether the release also changed shared data or settings before undoing anything.
Deployment · Lesson 5
Rollbacks
Learn to choose a known working version and check whether application rollback is sufficient.
Choosing a Previous Release
This example shows a new release followed by a failed request. The last verified version was 2. The reference labels below stand for complete image digests in an actual record.
08:50 version 2 digest-B homepage and version check passed
09:10 version 3 digest-C homepage check failed
Version 2 is a sensible rollback candidate if it still works with the environment. Use the recorded artifact identity to find it.
Which image would you investigate first as the rollback target?
Checking Data Compatibility
An application release may also change a database or another shared resource. Starting an older image leaves that external state as it is. Ask whether the older application can read the current data. If a data restore is needed, use the team's recovery plan and consider changes made since the backup.
Version 3 changed a database format. What must you check before starting version 2 against it?
Confirming the Result
After the rollback, verify the running version and repeat the same user-focused check that failed. Observe important dependencies again. Record the time, restored version, and results so someone can distinguish the original failure from the recovery.
The rollback command finished. Which pair supports that the service recovered?
Lesson complete
You finished Rollbacks
You can now plan a rollback around evidence.
Choose a release with a verified history.
Check shared data and configuration compatibility.
Verify the restored version and the affected user behavior.
Keep your learning progress
Create a free account to save this lesson and continue learning on any device.
Create a free account