Stuck Deployment rollout alerts
This feature is part of kwatch Pro, which is free during early access. See Community vs Pro.
A Deployment rollout replaces old Pods with new ones. If the new Pods cannot
become available, Kubernetes may report ProgressDeadlineExceeded. kwatch
watches that signal so the team can investigate the stalled rollout.
What kwatch detects
The rollout detector is part of kwatch Pro. It reports a Deployment that has exceeded its progress deadline. The alert points to the affected workload; the exact cause still depends on the new Pods and their Events.
There is no on/off switch for this detector: kwatch always watches every supported resource. To silence a known, intentional case use silences or a maintenance annotation (see General configuration).
Investigate a stuck rollout
Start with the Deployment and its rollout status:
kubectl rollout status deployment/<name> -n <namespace>
kubectl describe deployment <name> -n <namespace>
kubectl get pods -n <namespace>
Check the Deployment conditions and the new Pods. Image pull failures,
scheduling problems, container crashes, and readiness failures lead to
different fixes. Inspect a failing Pod with kubectl describe pod and its
recent logs before changing the rollout.
Related
See the Kubernetes coverage guide for related workload signals.