Kubernetes / Deployments, Scheduling & Batch Workloads
Find why a Kubernetes Deployment rollout stopped progressing
A rollout can remain incomplete because new Pods never become available or old replicas cannot terminate. Capture status with a bounded wait.
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 rollout status deployment/web --timeout=30sRead the result
This observes rollout progress without changing the Deployment. A timeout is the observer's limit, not proof the controller will never finish.
Resolve and verify
Inspect Deployment conditions, ReplicaSet events and failed Pods, then correct the demonstrated image, readiness or capacity problem. Verify the intended revision becomes available.
Before changing production
Do not repeatedly redeploy or roll back without checking configuration and database compatibility.