Node flaps between Ready and NotReady
Ready changes several times in a short window.
ImpactPods rescheduled again and again
Can it be seen coming?No
RupturaNot covered yet
How to detect it
Several Ready changes in 15 minutes.
Metrics and signals to watch:
kube_node_status_condition Ready
Can you see it coming?
No This failure arrives without a reliable warning sign, so the goal is to detect it fast and explain it.
What it hits next
every pod of the node.
What to do
Check the network and the kubelet of the node.
Sources
- kubernetes-mixin KubeNodeReadinessFlapping
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
- Node not ready
- Node under memory pressure
- 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