-
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
Fix usage of pre-existing VPCs via config file #447
Conversation
This comment has been minimized.
This comment has been minimized.
6d6e860
to
edc67bc
Compare
eu-north-1c: | ||
id: subnet-c123456 | ||
# must provide 'Private' and/or 'Public' subnets by availibility zone as shown | ||
Private: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should make this lowercase, but that would a bigger change and we'd have to bump the API version. Next time!
Integration test looking pass. |
edc67bc
to
b0f7cfd
Compare
- allow VPC ID to be passed via config file - validate VPC and subnet CIDRs - improve example config file - cleanup code, make it more consistent, add comments
b0f7cfd
to
9734c06
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
\o/
I still have the issue, the vpc and subnets already created. The code:
The error is in CF template ("Subnet Id is required"):
Am I doing something wrong? I want my nodes be in public subnet. |
Hi @pputnik , I think there might be a mistake in the cluster configuration you are using:
Let us know if that doesn't help! |
Hi @martina-if , thank you, I took uppercase version it from solution in one of the linked issues. |
Description
Checklist
make build
)make test
)