kubectl rollout status reports whether a resource rollout is still progressing, waiting for replicas to become ready, complete, or stalled. It waits while the controller updates the resource and prints a final status when the rollout finishes or exceeds its progress deadline. section 16.1.4 section 15.2.5
Use the command to:
- Watch a StatefulSet become ready, then investigate with kubectl get, kubectl describe, or kubectl logs if progress stops. section 16.1.4
- Follow a RollingUpdate as pods are replaced one at a time and readiness gates the next replacement. section 16.3.1
- Recognize a blocked update when a new pod fails its readiness probe; the rollout pauses until the pod becomes ready. section 16.3.1
- Detect a Deployment whose progress deadline was exceeded; the command reports the stall, while Kubernetes takes no further corrective action. section 15.2.5
Watching a StatefulSet rollout
Run `kubectl rollout status sts quiz`. During initialization it may print `Waiting for 3 pods to be ready...`. If the command does not complete, inspect readiness with `kubectl get pods -l app=quiz`, then use `kubectl describe` or `kubectl logs` to find the failing dependency or probe. After recovery, it can report `partitioned roll out complete: 3 new pods have been updated...`. section 16.1.4
A failed Deployment update
After a faulty update, `kubectl rollout status deploy kiada` can wait for new replicas and then report `error: deployment "kiada" exceeded its progress deadline`. Inspect the Deployment conditions to distinguish a stalled rollout from an update that is still progressing. section 15.2.5
