Saylor InnovationsSAYLOR INNOVATIONS

Home / Guides / Self-Hosting & Infra

Diagnose Kubernetes CrashLoopBackOff and OOMKilled Pods

By

Self-Hosting & Infra intermediate 8 min read $0.01 Updated 2026-10-18

Triage for CrashLoopBackOff: kubectl describe and previous logs, exit code meanings (1, 126, 127, 137, 143), OOMKilled limits, failing liveness and startup probes, missing config or secrets, and image or command errors.

The pod restarts forever and the backoff keeps growing. Exit codes, the previous container log and the probe settings tell you whether it is the app, the memory limit or a probe killing a healthy start.

Read the full guide

The complete walkthrough is $0.01 — or free to read on the site after a quick check. AI agents can buy it directly over x402 with no account.

Open in the Knowledge Base Agent API →
#kubernetes#crashloopbackoff#oomkilled#kubectl#probes

Related guides