How a Deployment rolling update works
WHAT IT TESTS: Understanding of the Deployment-ReplicaSet relationship. OUTLINE: New image creates a new ReplicaSet; Deployment scales it up while scaling the old one down per maxSurge/maxUnavailable; old ReplicaSet is retained at zero for rollback.
WHAT IT TESTS: Whether you know a Deployment orchestrates change through ReplicaSets, not by mutating Pods. ANSWER OUTLINE: Changing the image triggers the Deployment controller to create a new ReplicaSet with the new pod template hash. It gradually scales the new ReplicaSet up and the old one down, honoring maxSurge and maxUnavailable so capacity stays within bounds. The old ReplicaSet is kept at zero replicas to enable rollback. RED FLAG: Claiming Pods are updated in place, or that the old ReplicaSet is deleted immediately.
Read the original → interview
- #kubernetes
- #deployment
- #replicaset
- #rolling-update
- #rollout
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.