Node under memory pressure
Node condition MemoryPressure, the kubelet starts evicting.
ImpactPods evicted, first those above their requests
Can it be seen coming?Yes
RupturaPlanned
How to detect it
MemoryPressure True.
Metrics and signals to watch:
kube_node_status_condition MemoryPressurenode_memory_MemAvailable_bytes
Can you see it coming?
Yes Precursor: Available memory falling toward the eviction threshold.
What it hits next
pods of the node above their requests.
What to do
Set requests and limits, or add memory.
Sources
- Kubernetes node condition MemoryPressure
Where Ruptura stands
This failure is on the Ruptura roadmap. It is not reported yet.
Related failures
- Node not ready
- Node flaps between Ready and NotReady
- Node under disk pressure
- Node under PID pressure
- Node filesystem filling up
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