Closed dante286 closed 1 year ago
Thanks @dante286! Looks like you're right, at least in the Atlanta local zone, the local zone gets pulled first from the list of AZs, and also looks like managed node groups don't currently support local zones. Good catch!
I've created PR #103 to add this fix. Thanks!
If an AWS account has Local Zones enabled the VPC module will sometimes grab those zones for the subnets. It seems EKS is not yet supported in local zones and will cause the terraform applies to fail with the following error:
I have a workaround / fix that I've tested locally by applying a filter to the Availability Zones data resource to only get standard AZs:
I don't think Local Zones are heavily used yet, but I stumbled into this issue using a cloud sandbox on a learning platform and the provisioned sandbox happened to have a couple Local Zones enabled that led me to discovering this.