05 ANSWER-SAFE INCIDENT BRIEFS

Kubernetes and EKS incident practice

Train on CrashLoopBackOff, ImagePullBackOff, storage claims, Service selectors, and disruption-budget failures.

WHY THIS TRACK MATTERS

Debug the system, not the first plausible theory.

Kubernetes status names the stage where work stopped. Reading scheduler events, controller state, and object relationships beats debugging an application that never started.

  • Use Kubernetes state to choose the next check
  • Trace workload, Service, and storage relationships
  • Recover safely under rollout constraints

INCIDENT QUEUE

Choose the failure you want to face.

Each preview shows the symptom and baseline while keeping the diagnosis and recovery protected.

INC-043Intermediate

ConfigMap triggers a crash loop

Kubernetes · ConfigMap

new Pods cycle through CrashLoopBackOff after a configuration rollout
INC-044Foundational

The image cannot be pulled

Kubernetes · Registry

Pods remain in ImagePullBackOff after a release
INC-045Advanced

The claim waits for storage

Kubernetes · EBS CSI

stateful Pods remain Pending with unbound persistent-volume claims
INC-046Foundational

The Service selects nobody

Kubernetes · Service

a Service has no endpoints although Pods report Ready
INC-047Advanced

The disruption budget blocks maintenance

Kubernetes · PDB

node drain stalls because healthy Pods cannot be evicted

FULL SIMULATION LIBRARY

Train the decision, not just the vocabulary.

Three incidents are free. Core includes 100 incidents; Complete includes all 500 for lifetime access.

Start a free incident →