Deployment Strategies – Rolling Update: Near-Zero Downtime Without Double the Infrastructure josedacruz, April 11, 2026April 11, 2026 Rolling updates are the default Kubernetes deployment strategy — and for good reason. They give you near-zero downtime without requiring you to double your infrastructure. But they come with a catch most tutorials don’t explain: during the rollout, BOTH versions are live at the same time. In this video, we break down how rolling updates actually work, why maxSurge and maxUnavailable matter more than most engineers realise, and the one thing that makes or breaks a rolling deployment: the readiness probe. 🟡 Episode 2 of our 6-part Deployment Strategies series. If you haven’t seen Episode 1 (Recreate), start there to understand the baseline problem we’re solving. 📺 Full Deployment Strategies Series #1 → Recreate Deployment #2 → Rolling Update (you’re here) #3 → Blue/Green Deployment #4 → Canary Release #5 → A/B Testing Deployment #6 → Shadow Deployment Related architecture