-
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
Private/public subnet association with VPC routing tables #605
Comments
@Bulat-Gumerov Hey! I'm still trying to understand, but perhaps you're talking about the case that eksctl creates a VPC for you? And you want eksctl to automatically set up VPC peering between your existing VPC and the eksctl-created new VPC, that involves the said route table configuration. Am I following you correctly? |
Hey @mumoshu |
@Bulat-Gumerov how exactly did you fix this? Would you mind to share AWS CLI command, if that's what you used, just the exact steps you took to solve it. |
Ok, per our discussion on Slack, this is actually about the default route table, one that VPC gets automatically. We currently don't modify if in any way. I'll look into how we can fix this. |
also see https://aws.amazon.com/premiumsupport/knowledge-center/cloudformation-route-table-vpc/ for a potential work around to this |
eksctl
should explicitly associate private/publiс routing tables with same subnets that it creates. Current version 0.1.22 works only if you need single isolated VPC for k8s. But if you need to connect to another VPC you need to do network routing manually because there is no subnet association witheksctl
created routing tables.The text was updated successfully, but these errors were encountered: