Failure catalog · network level

DNS resolution fails

Lookups time out or return SERVFAIL.

ImpactCalls between services fail across namespaces
Can it be seen coming?Partly
RupturaPlanned

How to detect it

SERVFAIL or timeout rate high.

Metrics and signals to watch:

Can you see it coming?

Partly Precursor: CoreDNS saturated or its upstream failing.

What it hits next

every workload that resolves names.

What to do

Check CoreDNS pods, their limits and upstream resolvers.

Sources

Where Ruptura stands

This failure is on the Ruptura roadmap. It is not reported 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