Skip to content

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

Merged
merged 1 commit into from
Jul 23, 2018

Conversation

errordeveloper
Copy link
Contributor

@errordeveloper errordeveloper commented Jul 20, 2018

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.

Close #118. Finally.

@@ -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.

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.
Copy link
Contributor

@richardcase richardcase left a 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.

@@ -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.

@errordeveloper errordeveloper merged commit 6ae1b98 into master Jul 23, 2018
@errordeveloper errordeveloper deleted the zones-flag branch July 23, 2018 06:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

UnsupportedAvailabilityZoneException: lack of capacity to support cluster
2 participants