A city API Deployment cannot drop capacity during updates. The roll…

Question

A city API Deployment cannot drop capacity during updates. The rollingUpdate strategy sets maxUnavailable to 0 and maxSurge to 1. What behavior should the candidate expect?

Accepted Answer

Kubernetes creates one extra Pod above the desired count, then replaces old Pods only after new ones are Ready, so capacity never falls below the replica target. — Think of a bridge that must stay open while workers swap planks—you add one temporary plank before you remove any. With maxUnavailable 0 and maxSurge 1, the cluster surges by one Pod first and only drains an old Pod after the new one is Ready, so serving capacity never dips below the target.

Answer

Kubernetes immediately terminates all old Pods and waits for new ones, accepting a brief zero-capacity window.

Answer

maxUnavailable 0 blocks every rollout; the Deployment never creates new ReplicaSets until maxUnavailable is raised.

Answer

maxSurge 1 forces the Deployment to use the Recreate strategy instead of RollingUpdate.

A city API Deployment cannot drop capacity during updates. The rollingUpdate strategy sets maxUnavailable to 0 and maxSurge to 1. What behavior should the candidate expect?

Short Explanation

Full Explanation