Failure catalog · node level

Node not ready

The kubelet stops reporting or reports NotReady.

ImpactPods of the node are evicted after the toleration period
Can it be seen coming?Partly
RupturaNot covered yet

How to detect it

Ready not True for a sustained time.

Metrics and signals to watch:

Can you see it coming?

Partly Precursor: Memory, disk or PID pressure on the node.

What it hits next

every pod of the node.

What to do

Check the kubelet, the runtime and the node's resources.

Sources

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

This card is part of an open catalog of 66 Kubernetes and OpenShift failures. Correct it or add one on GitHub.

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