A small water-meter telemetry node pool is nearly full. During a Deployment roll, many new Pods sit Pending while capacity is exhausted. Which RollingUpdate knob most directly oversubscribed the pool?
Select an answer to reveal the explanation.
Short Explanation
maxSurge is permission to park extra new buses in the garage during the swap. On a tiny nearly full node pool, a wide surge asks for Pods that have nowhere to land—Pending. Tighten surge when workers are scarce; watch unavailability when you cannot afford darkness.
Full Explanation
RollingUpdate uses maxUnavailable to cap how many old Pods may be down and maxSurge to cap how many extra new Pods may exist during the roll. A high maxSurge on a small, nearly full water-meter node pool creates more new Pods than workers can place, so they stay Pending. maxUnavailable trades availability during the roll; it does not by itself oversubscribe capacity. revisionHistoryLimit and Service ports are unrelated to surge scheduling.