Incident Library?

API · MCP 한국어

Incident Library?

API · MCP 한국어

Component ?

ConfigMaps and Secrets

컨피그맵과 시크릿 · configmap

3 cases · 2019 to 2025

Root cause ?Configuration change 1 Hardware failure 1 Breaking change in an upgrade 1

Contributing factor ?Single point of failure 2 Unverified assumption 1 Change with a delayed effect 1 No headroom 1 Ineffective rollback 1 Deferred upgrades 1

Symptom ?Service outage 2 Scale-up failure 1 Container crash loop 1 DNS resolution failures 1 High error rate 1 Node NotReady 1

Cases, by severity

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
IL-0185 A disk failure made the first control plane node of a Kubespray cluster read-only, and recovery needed the Kubespray inventory reordered and a new control plane node joinedHans H. Kim · 2023
Root cause Hardware failure
IL-0066 Broken ConfigMap change lay dormant for weeks, then took down Pusher's edge proxy when a cluster upgrade replaced its podsPusher · 2019
Root cause Configuration change

View on the graph