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
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
Our VPC config looks like this:
For w/e reason eksctl creates private subnets with routing:
::/0 - igw-43243243242
This causes creation of managed node groups to fail due to AWS thinking those subnets are public and should have public IP assigned to nodes.
How to change the configuration to override subnet configuration to not assigne IGW to Private Subnets ?
From https://aws.amazon.com/premiumsupport/knowledge-center/configure-private-ipv6-subnet/ I could conclude that EKSCTL should have created Private Subnets with IPv6 Egress-Only Internet Gateways - instead it attached regular IGW to all Subnets.
Beta Was this translation helpful? Give feedback.
All reactions