Failure catalog · workload level

DaemonSet missing on some nodes

Fewer DaemonSet pods available than nodes that should run it.

ImpactNodes without logging, networking or monitoring agents
Can it be seen coming?No
RupturaCovered

How to detect it

Desired minus available above zero for a sustained time.

Metrics and signals to watch:

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

pods of the affected nodes.

What to do

Check taints, resources and pod errors on the missing nodes.

Sources

Where Ruptura stands

Ruptura reports this failure as the replicas_unavailable failure mode. A pre-registered lab test is not published yet.

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