Demo: an automated rollback on a failed health check
On This Lesson 3 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
watch a broken release revert with no human action. Prepares MID-055-LAB1.
Draft outline details
Step by step
- Show the pipeline promoting
ordersimage3f2a9c1from staging to production with a rolling strategy. - Deploy a deliberately broken version whose readiness endpoint fails.
- Planned mistake: the readiness probe returns 200 always, so the broken version takes traffic. Fix: make readiness check real dependencies and add a post-deploy smoke test.
- Watch the rollout halt and roll back automatically (for example
kubectl rollout undotriggered by the pipeline, or the rollout tool's analysis). - Review the timeline: detection time, rollback time, and the user impact on the dashboard.
Check your understanding
What detected the bad release?
Show answer
The failed readiness probe and post-deploy check, not a person.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.