You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use ENABLE_POD_ENI=true and ENABLE_PREFIX_DELEGATION=true to create a secondary ENI attached to our nodes in a dedicated subnet.
These subnets also have a number of CIDR reservations which we use for pods.
The issue we face is that randomly the primary address of the secondary ENI falls within the reserved CIDR ranges. This means more fragmentation of the subnet and wasted IP space. I am pretty sure that the reservation range that the primary address falls in becomes unusable for pods.
I can see that it doesn't request a specific address. Is it possible / a good idea to allow selecting a primary address from a range that is outside of any CIDR reservation?
The text was updated successfully, but these errors were encountered:
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
Problem:
We use
ENABLE_POD_ENI=true
andENABLE_PREFIX_DELEGATION=true
to create a secondary ENI attached to our nodes in a dedicated subnet.These subnets also have a number of CIDR reservations which we use for pods.
The issue we face is that randomly the primary address of the secondary ENI falls within the reserved CIDR ranges. This means more fragmentation of the subnet and wasted IP space. I am pretty sure that the reservation range that the primary address falls in becomes unusable for pods.
A solution?:
Looking at the code in
amazon-vpc-cni-k8s/pkg/awsutils/awsutils.go
Lines 891 to 910 in 0703d03
The text was updated successfully, but these errors were encountered: