search

aws / amazon-vpc-cni-k8s

Networking plugin repository for pod networking in Kubernetes using Elastic Network Interfaces on AWS
Apache License 2.0
2.25k stars 733 forks source link

Create secondary ENI when previous ENI isn't full due to lack of IPs in subnet - enhanced subnet discovery #2908

Closed jchen6585 closed 1 month ago

jchen6585 commented 4 months ago

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.

github-actions[bot] commented 2 months ago

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

github-actions[bot] commented 1 month ago

Issue closed due to inactivity.

yieon-lyon commented 1 month ago

If you provide this method, I think there will be any problems with IP loss for existing instances. But before understanding this, we must first carefully manage subnet configuration. with cidr ...

orsenthil commented 1 month ago

This is addressed in https://github.com/aws/amazon-vpc-cni-k8s

Edit: https://github.com/aws/amazon-vpc-cni-k8s/pull/2954

github-actions[bot] commented 1 month ago

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.

dougbyrne commented 3 weeks ago

I think the previous link was meant to be https://github.com/aws/amazon-vpc-cni-k8s/pull/2954