maxSurge=0 vs maxSurge=1 for fixed-capacity RollingUpdate with readiness probes
A small application is being migrated with a Kubernetes Deployment using RollingUpdate. The goal is to keep the Service available during the rollout while the cluster has a fixed capacity ceiling that cannot be exceeded. With maxSurge=0 the controller must terminate an old pod before a new one can be scheduled, which respects the resource ceiling but tempora
norg