-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Disable zone filter, add flag to set zones manually #131
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
Conversation
@@ -84,8 +84,8 @@ type AvailabilityZoneSelector struct { | |||
func NewSelectorWithDefaults(ec2api ec2iface.EC2API) *AvailabilityZoneSelector { | |||
avoidZones := map[string]bool{ | |||
// well-known over-populated zones | |||
"us-east-1a": true, | |||
"us-east-1b": true, | |||
// "us-east-1a": true, |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
5fc7bfa
to
7c4cb26
Compare
This the only sane way to fix UnsupportedAvailabilityZoneException, espcially because it turns out that this is somehow different in every AWS account (at least that what seems to be the case from the docs. > You may receive an error that one of the Availability Zones in your > request does not have sufficient capacity to create an Amazon EKS > cluster. If this happens, the error output contains the Availability > Zones that can support a new cluster. Retry creating your cluster > with at least two subnets that are located in the supported > Availability Zones for your account. In the future we may try parsing the error message and retrying automatically, but it doesn't seem feasible right now as we would need to improve some of the internals and provide stack update functionality.
7c4cb26
to
b0d98bd
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.
The change looks good.
@@ -84,8 +84,8 @@ type AvailabilityZoneSelector struct { | |||
func NewSelectorWithDefaults(ec2api ec2iface.EC2API) *AvailabilityZoneSelector { | |||
avoidZones := map[string]bool{ | |||
// well-known over-populated zones | |||
"us-east-1a": true, | |||
"us-east-1b": true, | |||
// "us-east-1a": true, |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
@@ -74,6 +75,8 @@ func createClusterCmd() *cobra.Command { | |||
fs.IntVarP(&cfg.MinNodes, "nodes-min", "m", 0, "minimum nodes in ASG") | |||
fs.IntVarP(&cfg.MaxNodes, "nodes-max", "M", 0, "maximum nodes in ASG") | |||
|
|||
fs.StringSliceVar(&availabilityZones, "zones", nil, "(auto-select if unspecified)") |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This the only sane way to fix UnsupportedAvailabilityZoneException,
espcially because it turns out that this is somehow different in every
AWS account (at least that what seems to be the case from the docs.
In the future we may try parsing the error message and retrying
automatically, but it doesn't seem feasible right now as we would
need to improve some of the internals and provide stack update
functionality.
Close #118. Finally.