1 Answer
- Newest
- Most votes
- Most comments
0
Hello,
Depending on which instance family and size you run, you have a constraint of number of IPs per ENI and a max number of ENI applies too.
As described here : https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html#AvailableIpPerENI
For example, a t3a.large instance is constrained to 3 ENI and 12 IPs per ENI at max.
Do you use the same instance family/size for your clusters in us-east-2 ?
For ref, a great blog post that explains the mechanisms of CNI IP allocation and how to manage the limits with prefixes.
https://aws.amazon.com/blogs/containers/amazon-vpc-cni-increases-pods-per-node-limits/
Thanks
answered 2 years ago
Relevant content
- Accepted Answerasked 2 years ago
- asked 5 years ago
- asked a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
yup I used the same family/size (t3a.large) in us-east-2. Hence my confusion that its behaving differently, but we have also noticed that the console in us-east-2 mentions prefixes for each network interface whereas the console in cn-northwest-1 does not. This makes me think that the prefix assignment feature is not available in the cn-northwest-1 region which could be the issue here possibly?
Hi, i don't see any region specific limitation for prefix assignment on my end.
If you already use this capability without any issue, then i would take a look at VPC CNI logs just to make sure the plugin can operate as expected for allocation.
ie: troubleshooting scenarios described here : https://docs.aws.amazon.com/eks/latest/userguide/cni-increase-ip-addresses.html