Incident Library

API · MCP 한국어

API and MCP kubegap Corrections and proposals

Incident Library

API · MCP 한국어

Component

VPC subnet or pod address range

VPC 서브넷 또는 파드 주소 범위 · subnet

3 cases · 2020 to 2025

Root cause Capacity exhaustion3

Contributing factor Unreviewed defaults3 No capacity planning2 Unverified assumption1 Unknown limit1 Harmful manual action1 Retry storm1 Ineffective rollback1

Symptom IP address exhaustion3 Pods Pending3 Scale-up failure1

Organisation Adevinta1 loveholidays1 Neon1

Cases, by severity

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-0015 A GKE cluster's /16 pod address range ran out at 256 nodes, leaving new pods Pending and node scale-ups failing

View on the graph

loveholidays · 2020

Root cause Capacity exhaustion