-
Notifications
You must be signed in to change notification settings - Fork 466
kube-aws up fails using multiple AZ/Subnets #510
Comments
@colhom I believe that validation fails when Should we switch which instanceCIDR to validate(top-level/under subnets) according to |
@harsha-y Any luck? Can we close this? |
We ran into #538 as well. Giving it another shot today with both release 0.7.1 and 855a0f9 binaries. With 0.7.1 we get the same error as #538 - is our assumption that kube-aws can launch cluster into an existing VPC with existing subnets in multiple availability zones incorrect? We are using 3 private /24 subnets. With latest master 855a0f9 we get the following error. Changing this to alpha results in the same error. |
I just replied on #538 about the first error, I believe currently we don't support existing subnets, just existing VPCs. For the second error, I suspect coreos.com may have been down briefly as I've heard talks of ec2 outages. Currently kube-aws pulls the alphaami information from |
kube-aws validate succeeds without any errors. kube-aws up fails.
kube-aws version -
Error -
Configuration -
The text was updated successfully, but these errors were encountered: