hard20 pts · first answer countskubernetesdeployment-strategies

Rolling update that never finishes

A Deployment uses maxUnavailable: 0 and maxSurge: 1. The cluster has no spare capacity and no autoscaler. What happens during a rollout?

A.Kubernetes deletes an old Pod first to make room, then starts the new one.B.The rollout finishes instantly because maxSurge is ignored when the cluster is full.C.Kubernetes evicts Pods from other Deployments to make space.D.The new surge Pod stays Pending, no old Pod is removed, and the rollout stalls until progressDeadlineSeconds marks it as failed.

← Removing an item from a count list Hotfix keeps disappearing →