Skip to content

Archive Topic Map

Troubleshooting

This shelf is built to be used mid-incident: symptom → what it means → proof commands → smallest safe fix → related doctrine.

All topic mapsShrine ArchiveLearning Path

Orientation

A curated shelf for study and for retrieval.

The discipline of diagnosis

Troubleshooting is not creativity. It is evidence collection and constraint elimination.

If you can’t state the symptom precisely, you can’t confirm the fix.

  • Read events early; they often name the failure.
  • Prove endpoints before you debug networking internals.
  • Distinguish readiness (traffic gate) from liveness (restart trigger).

Atlas (fast entries)

Symptom-first references structured for speed.

Atlas

Troubleshoot

Pods in CrashLoopBackOff

Exit codes, probes, dependencies, and smallest-safe resolutions.

Atlas

Troubleshoot

Service Has No Endpoints

Selectors, readiness gating, ports, EndpointSlices.

Atlas

Troubleshoot

Node NotReady

Containment first: conditions, cordon/drain posture, failure domains.

Labs (repeatable practice)

Make the diagnostic sequence physical before you need it.

Lab

Lab

CrashLoopBackOff Triage

Evidence-first classification and smallest-safe fixes.

Lab

Lab

Fix a Broken Service Selector

Selectors, endpoints, ports, and readiness.

Lab

Lab

Pending Pods (Scheduling Constraints)

Read scheduler events and fix the governing constraint.

Related maps

Adjacent shelves for continued study.

Topic map

Map

Operations

Continue with the adjacent shelf.

Topic map

Map

Networking

Continue with the adjacent shelf.

Topic map

Map

Scheduling & Placement

Continue with the adjacent shelf.

Canonical link

Canonical URL: /library/topics/troubleshooting