-
Notifications
You must be signed in to change notification settings - Fork 742
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create secondary ENI when previous ENI isn't full due to lack of IPs in subnet - enhanced subnet discovery #2908
Comments
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days |
Issue closed due to inactivity. |
If you provide this method, I think there will be any problems with IP loss for existing instances. |
This is addressed in https://github.com/aws/amazon-vpc-cni-k8s Edit: |
This issue is now closed. Comments on closed issues are hard for our team to see. |
I think the previous link was meant to be #2954 |
What would you like to be added:
When enhanced subnet discovery is enabled, we should create a secondary ENI using a new subnet (if there is one available) when the previous ENI is failing to add more IPs due to lack of IPs in subnet.
Why is this needed:
This will prevent IPAMD from being stuck trying to allocate IPs to the previous ENI even if the subnet is out of IPs.
The text was updated successfully, but these errors were encountered: