Skip to main content

Tag: EKS

Amazon Elastic Kubernetes Service

IDTitleDescriptionCategoryTechnologyTags
CRE-2025-0061
Medium
Impact: 7/10
Mitigation: 4/10
Karpenter Stability Issues on EKS During Leader Election
  • EKS may be able to handle steady, predictable scale, but struggles during large‑scale auto scaling events when many workloads and nodes are spinning up or down simultaneously.
  • This instability affects components that implement leader election using the Kubernetes API, such as:
  • aws‑load‑balancer‑controller
  • karpenter
  • keda‑operator
  • ebs‑csi‑controller
  • efs‑csi‑controller
Stability ProblemskarpenterKarpenterKEDAAWSEKS
CRE-2025-0112
Critical
Impact: 10/10
Mitigation: 4/10
AWS VPC CNI Node IP Pool Depletion Crisis
Critical AWS VPC CNI node IP pool depletion detected causing cascading pod scheduling failures.This pattern indicates severe subnet IP address exhaustion combined with ENI allocation failures,leading to complete cluster networking breakdown. The failure sequence shows ipamd errors,kubelet scheduling failures, and controller-level pod creation blocks that render clustersunable to deploy new workloads, scale existing services, or recover from node failures.This represents one of the most severe Kubernetes infrastructure failures, often requiringimmediate manual intervention including subnet expansion, secondary CIDR provisioning,or emergency workload termination to restore cluster functionality.
VPC CNI Problemsaws-vpc-cniAWSEKSKubernetesNetworkingVPC CNIAWS CNIIP ExhaustionENI AllocationSubnet ExhaustionPod Scheduling FailureCluster ParalysisAWS API LimitsKnown ProblemCritical InfrastructureService OutageCascading FailureCapacity ExceededScalability IssueRevenue ImpactCompliance ViolationThreshold ExceededInfrastructurePublic