Day111 part3

Name: Summarizer.tube
Author: Summarizer.tube

20 min video·en·May 14, 2026

Summary

The video explains how Kubernetes Deployments perform rolling updates by default, how to control them with maxUnavailable and maxSurge, and contrasts rolling, recreate, blue‑green, and canary deployment strategies.

Key Points

—ReplicaSets do not support rolling updates; only Deployments provide that capability.
—Blue‑green and canary deployments are alternative strategies that aim to reduce downtime, but they were only introduced briefly and will be covered later.
—The video demonstrates the rolling update process with kubectl apply -f deploy.yaml, showing pods being created and deleted sequentially.
—By default, a Deployment performs a rolling update, replacing pods incrementally instead of deleting all at once.
—Setting maxUnavailable to 25% means only one pod out of four can be unavailable at any time during the update.
—Setting maxSurge to 25% means one extra pod can be created above the desired replica count while the old pod is being terminated.
—Rolling updates can be customized using the maxUnavailable and maxSurge fields to control how many pods are taken down or added during the update.
—If maxUnavailable and maxSurge are both set to 100%, the Deployment behaves like a recreate strategy, deleting all old pods before creating new ones, causing downtime.
—The watch command can be used to monitor pod status (Creating, Running, Terminating, etc.) during the update.
—The overall goal of these strategies is to maintain high availability while deploying new container images.

Copy All

Share Link

Share as image

Day111 part3

Key Points

—ReplicaSets do not support rolling updates; only Deployments provide that capability.

—Blue‑green and canary deployments are alternative strategies that aim to reduce downtime, but they were only introduced briefly and will be covered later.

—The video demonstrates the rolling update process with kubectl apply -f deploy.yaml, showing pods being created and deleted sequentially.

—By default, a Deployment performs a rolling update, replacing pods incrementally instead of deleting all at once.

—Setting maxUnavailable to 25% means only one pod out of four can be unavailable at any time during the update.

—Setting maxSurge to 25% means one extra pod can be created above the desired replica count while the old pod is being terminated.

—Rolling updates can be customized using the maxUnavailable and maxSurge fields to control how many pods are taken down or added during the update.

—If maxUnavailable and maxSurge are both set to 100%, the Deployment behaves like a recreate strategy, deleting all old pods before creating new ones, causing downtime.

—The watch command can be used to monitor pod status (Creating, Running, Terminating, etc.) during the update.

—The overall goal of these strategies is to maintain high availability while deploying new container images.

Summarize any YouTube video

Summarizer.tube

Bookmark