[Bug] creating a cluster using the local zone example fails

[antevens]

What were you trying to accomplish?

Create EKS cluster with localZones defined

ant@antimatter:~/tmp/test.eks$ cat 33-local-zones.yaml 
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig

metadata:
  name: cluster-33
  region: us-west-2

localZones: ["us-west-2-lax-1a", "us-west-2-lax-1b"]

nodeGroups:
  - name: local-ng
    localZones: ["us-west-2-lax-1a", "us-west-2-lax-1b"]
ant@antimatter:~/tmp/test.eks$ eksctl create cluster -f 33-local-zones.yaml
2025-01-30 10:57:44 [ℹ]  eksctl version 0.202.0
2025-01-30 10:57:44 [ℹ]  using region us-west-2
2025-01-30 10:57:44 [ℹ]  setting availability zones to [us-west-2b us-west-2c us-west-2d]
Error: error describing availability zones: operation error EC2: DescribeAvailabilityZones, https response error StatusCode: 400, RequestID: f5db1c3d-1a5e-4eaa-bbac-573f42746f9e, api error InvalidParameterValue: Invalid availability zone: [us-west-2-lax-1a]
ant@antimatter:~/tmp/test.eks$ 

What happened?

Some part of the creation process is trying to use/validate localZones instead of using availabilityZones

How to reproduce it?

Create a cluster using the 33-local-zones.yaml example file from https://github.com/eksctl-io/eksctl/blob/main/examples/33-local-zones.yaml

Versions

ant@antimatter:~/tmp/test.eks$ eksctl info
eksctl version: 0.202.0
kubectl version: v1.31.5
OS: linux

[github-actions]

Hello antevens 👋 Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website