ProgressDeadlineExceeded Kubernetes Origin: Platform & cloud Last updated 12 Oct 2026

deployment "x" exceeded its progress deadline (ProgressDeadlineExceeded)

A rollout didn’t make progress within progressDeadlineSeconds (default 600) — new pods never became ready.

Exact message you may see exceeded its progress deadlineerror: deployment "web" exceeded its progress deadline
Explore the map of this error Full error map →
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

  1. Find the new pods’ state: kubectl get rs and pods
  2. Fix the underlying pod error
  3. Roll back: kubectl rollout undo

Detailed fix by platform

Kubernetes

  1. 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

  1. New pods — Status of pods in the newest ReplicaSet
  2. Events — FailedCreate/Unhealthy
  3. 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:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

1104 — Cloudflare Error 1104: A variation of this script was not found (Worker route to deleted script) (Cloudflare)1104another operation is in progress — Error: UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress (Kubernetes)another operation is …CrashLoopBackOff — Kubernetes: CrashLoopBackOff (Kubernetes)CrashLoopBackOffEnvironment health has transitioned to Severe — Elastic Beanstalk: Environment health has transitioned from Ok to Severe (AWS)Environment health ha…field is immutable — The Deployment is invalid: spec.selector: Invalid value: field is immutable (Kubernetes)field is immutableImagePullBackOff — Kubernetes: ImagePullBackOff / ErrImagePull (Kubernetes)ImagePullBackOffInvalidTemplateDeployment — ARM/Bicep: DeploymentFailed / InvalidTemplateDeployment / InvalidTemplate (Azure)InvalidTemplateDeploy…Multi-Attach error — Multi-Attach error for volume: Volume is already exclusively attached to one node and can't be attached to another (Kubernetes)Multi-Attach errorProgressD…

Explore the map of this error Full error map →

🧠 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.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.