Sudden memory jump past the limit
Memory jumps from a normal level past the limit with no trend before.
ImpactOOM kill with no warning from a trend rule
Can it be seen coming?Partly
RupturaCovered
How to detect it
Last termination reason is OOMKilled.
Metrics and signals to watch:
kube_pod_container_status_last_terminated_reason
Can you see it coming?
Partly Precursor: Only a regular rhythm of past kills; the jump itself gives no warning.
What it hits next
callers of the workload.
What to do
Raise the memory limit or find the request that spikes memory.
Sources
- Kubernetes termination reason OOMKilled
Where Ruptura stands
Ruptura reports this failure as the oom_killed failure mode. A pre-registered lab test is not published yet.
Related failures
- Memory leak ends in an OOM kill
- Memory growth accelerates toward the limit
- Container killed by OOM again and again
- Container crashes at start, again and again
- Failures that come back at a regular interval
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