Skip to content
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

Feature request: Cross account ENIs is more complex than just 5 free IPs #24

Closed
bryantbiggs opened this issue Feb 23, 2023 · 1 comment · Fixed by #38
Closed

Feature request: Cross account ENIs is more complex than just 5 free IPs #24

bryantbiggs opened this issue Feb 23, 2023 · 1 comment · Fixed by #38
Labels
feature-request Request for a new feature

Comments

@bryantbiggs
Copy link
Member

bryantbiggs commented Feb 23, 2023

Use case

Currently, its required to have at least 5 free IPs for the control plane cross account ENIs to facilitate an upgrade. However, this isn't the full story since the cross account ENIs will be created in at least 2 different availability zones.

Solution/User Experience

Change EKS001 check to ensure there are at least two subnets in different AZs with at least 4 available IPs each for the control plane cross account ENIs - awsdocs/amazon-eks-user-guide#688

Alternative solutions

Use current guidance of 5 free IPs but this is mis-leading (if you only have 5 free IPs, but all in one subnet, the upgrade would fail)

@bryantbiggs bryantbiggs added triage feature-request Request for a new feature and removed triage labels Feb 23, 2023
@bryantbiggs bryantbiggs moved this to Todo in eksup Feb 23, 2023
@bryantbiggs
Copy link
Member Author

Check should be updated to ensure at least 5 free IPs in two subnets in different availability zones used by the control plane

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for a new feature
Projects
Status: Done
1 participant