Kubernetes documentation (opens in a new tab)
The official reference for the tools used in this lesson.
Link
Rolling deploys and rollbacks
A rolling update replaces pods gradually so there is no downtime. The important half is being able to reverse it in seconds.
Lesson 3.28m 44sAdvanced5.5k students
Chapters
8:44- 0:00Introduction
- 0:24Why Rolling Updates & Rollbacks matter in Kubernetes
- 0:57Demo: Performing a Rolling Update with kubectl
- 3:10Behind the Scenes: How Kubernetes manages Rolling Updates
- 3:36Demo: Rolling Back to a Previous Deployment
- 4:51Handling a Buggy Application with Rollback
- 7:11Tracking Rollout History in Kubernetes
- 7:36When to Use Rolling Updates vs Rollbacks
- 8:18Conclusion & Best Practices
What this lesson covers
- Configure a rolling update and its surge settings
- Compare rolling, blue-green, and canary strategies
- Roll back quickly and predictably
This lesson sits in Continuous Delivery, part of DevOps with Docker and Kubernetes. It assumes what came before it and leads directly into the next lesson in the module.
In this lesson you will
- Configure a rolling update and its surge settings
- Compare rolling, blue-green, and canary strategies
- Roll back quickly and predictably
Resources
Personal notes are coming soon.