deployment "x" exceeded its progress deadline (ProgressDeadlineExceeded)
A rollout didn’t make progress within progressDeadlineSeconds (default 600) — new pods never became ready.
Seen on:
Kubernetes
Meaning
kubectl rollout status and CD tools fail with this. The Deployment itself is fine; the new ReplicaSet’s pods are stuck — ImagePullBackOff, CrashLoopBackOff, failing readiness, Pending for resources or quota.
Common causes
- New pods crash or fail readiness
- Image can’t be pulled
- Insufficient resources/quota for new pods
- Very slow startup with a short deadline
⚡ Quick fix
- Find the new pods’ state: kubectl get rs and pods
- Fix the underlying pod error
- Roll back: kubectl rollout undo
Detailed fix by platform
Kubernetes
- bash
kubectl rollout status deploy/web -n app kubectl get pods -n app -l app=web kubectl rollout undo deploy/web -n app
How to diagnose
- New pods — Status of pods in the newest ReplicaSet
- Events — FailedCreate/Unhealthy
- Deadline — progressDeadlineSeconds
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Kubernetes
- error converting YAML to JSON error converting YAML to JSON: yaml: line 12: did not find expected key
- is waiting to start Error from server (BadRequest): container "x" in pod "y" is waiting to start: ContainerCreating
- kubectl connection refused kubectl: The connection to the server localhost:8080 was refused — did you specify the right host or port?
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026