# A Deployment managed by Argo CD rolls out an image tag that doesn't exist, and progressDeadlineSeconds is left at its default. When does Argo CD report the Deployment as Degraded?

Argo CD, Hard (Expert), Troubleshooting & Debugging. https://k8wiz.com/uquiz/a-deployment-managed-by-argo-cd-rolls-out-an-image-tag-that-doesnt-exist-and-progressdeadlineseconds-is-left-at-its-default-when

- A. After 600 seconds, once Kubernetes reports ProgressDeadlineExceeded
- B. At once, as soon as the new Pods show ImagePullBackOff in their status
- C. After the next hard refresh, once the repo-server regenerates manifests
- D. Never, since Argo CD only reports Deployments Progressing or Healthy

**Answer:** After 600 seconds, once Kubernetes reports ProgressDeadlineExceeded

**Explanation:** Argo CD's Deployment check follows kubectl rollout status and judges the Deployment from its own status, not from its Pods. It reports Progressing while updated replicas aren't available, and Degraded only when the Progressing condition has the reason ProgressDeadlineExceeded. Kubernetes sets that after progressDeadlineSeconds, which defaults to 600, so lower it if you want failed rollouts to show up sooner.