CronJob misses its schedule
No successful run in the expected interval, runs overlap or are suspended.
ImpactScheduled work silently stops
Can it be seen coming?Yes
RupturaNot covered yet
How to detect it
Last successful run older than the schedule allows.
Metrics and signals to watch:
kube_cronjob_status_last_schedule_timekube_cronjob_next_schedule_time
Can you see it coming?
Yes Precursor: Run duration growing toward the schedule interval.
What it hits next
consumers of the job's output.
What to do
Check suspension, concurrency policy and the last runs.
Sources
- Kubernetes CronJob status
Where Ruptura stands
Ruptura does not cover this failure yet. The card is here so you know it exists and how to detect it.
Related failures
- Workload missing replicas
- StatefulSet missing replicas
- DaemonSet missing on some nodes
- Rollout passes its progress deadline
- New release leaks memory the previous one did not
See it coming instead of reading about it
Ruptura is an open-source operator for Kubernetes and OpenShift that predicts the failures in this catalog that can be predicted, detects the others, and sends them to Alertmanager. Watch an OOM crash predicted 21 minutes early · ★ GitHub
Ruptura is an open-source operator for Kubernetes and OpenShift that predicts the failures in this catalog that can be predicted, detects the others, and sends them to Alertmanager. Watch an OOM crash predicted 21 minutes early · ★ GitHub