I've deployed under 650 Pods on less than 100 nodes in my EKS setup, all within a subnet that has a CIDR range of `10.0.20.0/22`. This configuration should theoretically offer up to 1024 IP addresses. Despite this, I'm getting a notification that no IP addresses are available. I'm trying to figure out what's consuming all the available IPs—any insights would be greatly appreciated!
2 Answers
A common mistake with EKS is not starting with a sufficiently large subnet. I'd recommend using at least a /19 CIDR block to avoid these problems in the future.
Consider implementing a separate CIDR for your pods within the VPC. Look into using AWS_VPC_K8S_CNI_CUSTOM_NETWORK_CFG and ENABLE_PREFIX_DELEGATION. This way, you can allocate a larger CIDR specifically for pods, enhancing IP allocation speed whenever a Pod starts! Just remember to manage the routing accordingly as your nodes will NAT traffic from pods to the internet (if you're using the default configuration).
Related Questions
How To Get Your Domain Unblocked From Facebook
How To Find A String In a Directory of Files Using Linux