ProgressDeadlineExceeded
The Deployment controller marked the rollout as failed because no new pod became available for progressDeadlineSeconds (default 600). Kubernetes stops here; it doesn’t roll back.
Diagnose in order
Section titled “Diagnose in order”- Find the new ReplicaSet (highest revision):
kubectl get rs -l app=web --sort-by=.metadata.creationTimestamp. - Look at its pods:
kubectl get pods -l app=weband pick the newest. Their state names the real problem:ImagePullBackOff,CrashLoopBackOff,Pending, orRunningbut not Ready. - If no new pods exist at all, the ReplicaSet couldn’t create them:
kubectl describe rs <new-rs>shows quota or Pod Security rejections.
Roll back, then fix forward
Section titled “Roll back, then fix forward”kubectl rollout undo deployment/webkubectl rollout status deployment/webWith GitOps, revert the commit instead, or the controller will reapply the broken version.
Then follow the error page for whatever state the new pods were in.
Read next: Deployments and rollouts.