Failure catalog · container level

Init container keeps failing

The pod stays in Init, its init container crashes or waits on a dependency.

ImpactThe pod never starts
Can it be seen coming?No
RupturaNot covered yet

How to detect it

Init container restarts or waits 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

callers of the workload.

What to do

Read the init container logs, often a dependency that is not reachable.

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