Incident Library

API · MCP 한국어

API and MCP kubegap Corrections and proposals

Incident Library

API · MCP 한국어

Symptom

IP address exhaustion

IP 주소 고갈 · no-available-ip

6 cases · 2020 to 2025

Root cause Capacity exhaustion3 Configuration change3

Component AWS VPC CNI5 Node pool4 VPC subnet or pod address range3 Cluster autoscaler2 CoreDNS1

Contributing factor Unreviewed defaults3 No capacity planning2 No configuration tests2 Unverified assumption1

Organisation UK Ministry of Justice2 Adevinta1 CoW Protocol1 loveholidays1

Cases

IL-0006 VPC subnets ran out of IP addresses because the AWS VPC CNI kept IPs on full nodes, and WARM_IP_TARGET changes then blocked pod starts after every pod deletionNeon · 2025
Root cause Capacity exhaustion
IL-0007 The AWS VPC CNI could not assign IP addresses to pods as an EKS cluster ran out of IPv4 spaceAdevinta · 2024
Root cause Capacity exhaustion
IL-0114 An unpinned AWS VPC CNI plugin was updated automatically during a capacity expansion, leaving new pods Pending without IP addresses and stopping CoW Protocol settlements for about 3.5 hours

View on the graph

Node launch template1

Node root disk1

Harmful manual action1

No alert on limit1

Overlapping failures1

Ineffective rollback1

Missed in review1

Unpinned version1

CoW Protocol · 2024

Root cause Configuration change

IL-0019 An EKS Terraform module upgrade shrank node root disks from 100 GB to 20 GB and image pulls failed with no space left on deviceUK Ministry of Justice · 2023

Root cause Configuration change

IL-0017 AWS VPC CNI stopped allocating pod IP addresses on six nodes of the live cluster, leaving new pods in ContainerCreatingUK Ministry of Justice · 2023

Root cause Configuration change

IL-0015 A GKE cluster's /16 pod address range ran out at 256 nodes, leaving new pods Pending and node scale-ups failingloveholidays · 2020

Root cause Capacity exhaustion