Container crash loop

Cases

1. IL-0183 kubeadm's one-year leaf certificates expired, so kube-apiserver could not reach etcd, restarted in a loop and left the cluster unreachableckck803 · 2026

   Root cause Certificate or credential expiry

2. IL-0100 PostHog's feature flags pods were packed onto Kubernetes nodes that were too small for their CPU requests, and CPU saturation above 90% caused three outages in ten days through Redis overload, connection pool exhaustion and slow queriesPostHog · 2025

   Root cause Capacity exhaustion

3. IL-0187 A brief Spring Cloud Config Server downtime failed every client application's liveness probe, because the actuator health check included the config server, and Kubernetes restarted the pods in a kill loopYonghyun Kim · 2025

   Root cause Dependency failure

4. IL-0101 After Google forced a GKE control plane upgrade to 1.33.2 at a deprecation deadline, no new node could initialise, so autoscaling and spot node replacement stopped for 15 hoursWealthy · 2025 · sev1

   Root cause Breaking change in an upgrade

5. IL-0122 An invalid value in a configuration shared by several ChatGPT services put pods into crash loops and raised error ratesOpenAI · 2025

   Root cause Configuration change

6. IL-0067 Redis filled its persistent volume, corrupted its append-only file and crash-looped on every restartBC Government · 2025 · sev1

   Root cause Capacity exhaustion