chilly-photographer-60932
12/22/2018, 1:02 AMaws:eks:Cluster (cluster-eksCluster):
error: Plan apply failed: error creating EKS Cluster (cluster-eksCluster-f2f0a42): UnsupportedAvailabilityZoneException: Cannot create cluster 'cluster-eksCluster-f2f0a42' because us-east-1e, the targeted availability zone, does not currently have sufficient capacity to support the cluster. Retry and choose from these availability zones: us-east-1a, us-east-1b, us-east-1c, us-east-1d, us-east-1f
status code: 400, request id: 25e1928f-0585-11e9-860f-afb328b78912
white-balloon-205
us-east-1
region in one AZ.
The current new Network
we have doesn't let you pick the AZs manually, it just ets you pick how many AZs. So we don't have a direct way to ensure that you avoid this one AZ. We're tracking adding this in https://github.com/pulumi/pulumi-aws-infra/issues/32. You could create the VPC manually and avoid that AZ if needed, or use a different region that does not have these capacity limitations.
There's a note on the general issue for new eks.Cluster
in the example README: https://github.com/pulumi/examples/tree/master/aws-ts-eks#steps.chilly-photographer-60932
12/22/2018, 9:36 PMeks
feels not matured enough compared to gke