-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 ipv6 subnets for created VPC #566
Comments
Hi @VincentCouzij! To be clear, this won't enable IPv6 for pods, just for ELB/ALB? |
@errordeveloper Yes only for the created VPC so ELB and ALB's can use dualstack. |
Thanks! Am I understanding correctly that you'd be looking to have IPv6 enabled for the set of subnets eksctl currently creates (not separate set of subnets)? And would be okay to keep IPv6 disabled for the EC2 instances? Out of curiosity - would you be looking to use Kubernetes with IPv6 also, or ingress is all that matters? |
Yes add ipv6 CIDR to each created subnet in the default setup. In our setup EC2 instances don't need their own ipv6 address. All traffic is routed through ALB's. For now it's just ingress. |
I'm going to start looking into this and will open WIP PR once I have something going. |
@VincentCouzij see #776, it appears to work, but I will need to review a few things and write some tests. Feel free to reach out on slack if you have time to test it. |
Why do you want this feature?
To be able to create dualstack load balancers in the created VPC (Our api needs to be accessible via ipv6). I am currently adding the IPv6 CIDR's to the subnets manually but would like this process automated with eksctl.
What feature/behavior/change do you want?
Options for adding IPv6 CIDR's to vpc/subnets and route table setup for ipv6 to the internet gateway.
The text was updated successfully, but these errors were encountered: