Kubernetes / Deployments, Scheduling & Batch Workloads
Investigate a rolling update blocked by temporary capacity demand
A Deployment can need extra replicas during an update even when its steady-state size fits. Inspect rollout strategy and scheduling evidence.
Environment and inputs: Kubernetes · kubectl with supported client/server versions and delegated RBAC. Examples use namespace app unless noted. Check context, namespace, APIs and provider support first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
kubectl -n app describe deployment webRead the result
The strategy, replica counts and events help expose surge and availability constraints. Pod requests and cluster policy determine whether new replicas fit.
Resolve and verify
Compare maxSurge, maxUnavailable and real schedulable capacity. Plan justified capacity or an approved strategy change while preserving service availability.
Before changing production
Do not lower availability guarantees or delete all old replicas merely to free space for an unready release.