Incident Library?

Incident Library?

Component ?

Cluster autoscaler 클러스터 오토스케일러 · `cluster-autoscaler`

5 cases · 2019 to 2025

Root cause ?Capacity exhaustion 2 Cloud provider outage 1 Faulty deployment 1 Software defect 1

Contributing factor ?Unreviewed defaults 4 No headroom 2 Unknown limit 1 No alert on limit 1 No capacity planning 1 No safeguard on destructive change 1 Overlapping failures 1 Retry storm 1 Ineffective rollback 1 Unrepresentative staging 1

Symptom ?Pods Pending 3 Service outage 3 IP address exhaustion 2 Upgrade stall 2 Autoscaler misbehaviour 1 Scale-up failure 1 Database overload 1 High latency 1 Pod eviction 1

Cases, by severity

IL-0020 A descheduler evicted pods from cordoned nodes during an EKS upgrade — UK Ministry of Justice, 2025, sev1
Root cause Faulty deployment
IL-0024 Hub outage from expensive cache queries and uncancelled requests — Hugging Face, 2024, sev1
Root cause Software defect
IL-0015 A GKE pod address range ran out at 256 nodes — loveholidays, 2020, sev3
Root cause Capacity exhaustion
IL-0006 IP exhaustion with the AWS VPC CNI, then a warm-pool setting cascade — Neon, 2025
Root cause Capacity exhaustion
IL-0014 A GKE upgrade that stalled, left zombie nodes and broke an ingress — loveholidays, 2019
Root cause Cloud provider outage

View on the graph