Skip to content
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

[Bug] Launching self-managed node group in Local Zones fail if account is allow-listed to Wavelength Zones and Local Zones #7202

Closed
rhbelson opened this issue Oct 19, 2023 · 5 comments · Fixed by #7204
Assignees
Labels

Comments

@rhbelson
Copy link

What were you trying to accomplish?

In trying to launch a self-managed node group in Local Zones, I used

eksctl create cluster --timeout 30m0s -f - << EOF
---
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig
metadata:
  name: ${CLUSTER_NAME}
  region: ${AWS_REGION}
  version: "1.25"
  tags:
    environment: ${CLUSTER_NAME}
localZones: ["us-west-2-lax-1a", "us-west-2-las-1a"]
nodeGroups:
  - name: local-ng
    localZones: ["us-west-2-las-1a"]
    instanceType: t3.xlarge
    desiredCapacity: 1
    minSize: 0
    maxSize: 3
    volumeType: gp2
managedNodeGroups:
  - instanceType: c6g.xlarge
    amiFamily: AmazonLinux2
    name: ${CLUSTER_NAME}-ng
    desiredCapacity: 0
    minSize: 0
    maxSize: 3
iam:
  withOIDC: true
EOF

What happened?

eksctl failed to create the node group because of the following error:

2023-10-19 18:31:05 [✖]  could not find public subnets for zones ["us-west-2-las-1a"] (allSubnets=v1alpha5.AZSubnetMapping{"us-west-2-las-1a":v1alpha5.AZSubnetSpec{ID:"subnet-0ff0cac384615f1f2", AZ:"us-west-2-las-1a", CIDR:(*ipnet.IPNet)(0xc000c552c0), CIDRIndex:0, OutpostARN:""}, "us-west-2-lax-1a":v1alpha5.AZSubnetSpec{ID:"subnet-0fbfc2d5a0c70cc05", AZ:"us-west-2-lax-1a", CIDR:(*ipnet.IPNet)(0xc000c555c0), CIDRIndex:0, OutpostARN:""}} localZones=[]string{"us-west-2-las-1a"} subnets=[]string(nil)): failed to select subnet us-west-2-las-1a: error discovering zone types: expected zone type to be local or AZ; got wavelength-zone

The error message reads got wavelength-zone, however the subnet in reference (subnet-0fbfc2d5a0c70cc05) is 100% a Local Zone (see below):

aws ec2 describe-subnets --subnet-id subnet-0fbfc2d5a0c70cc05
{
    "Subnets": [
        {
            "AvailabilityZone": "us-west-2-lax-1a",
            "AvailabilityZoneId": "usw2-lax1-az1",
            "AvailableIpAddressCount": 4091,

When recreating this cluster from an AWS Account only allow-listed to Local Zones but not Wavelength Zones, no such error occurs.

Versions

$ eksctl info

eksctl version: 0.162.0
kubectl version: v1.22.6-eks-7d68063
OS: linux
@github-actions
Copy link
Contributor

Hello rhbelson 👋 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

@cPu1
Copy link
Collaborator

cPu1 commented Oct 20, 2023

I have opened a PR with a fix. There's another PR open that adds support for Wavelength zones but we haven't had a chance to fully consider its ramifications or test it yet.

@rhbelson
Copy link
Author

rhbelson commented Oct 23, 2023

Thanks @cPu1! Would there be any test cases that the reviewers could use when reviewing the PR?

Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the stale label Nov 23, 2023
Copy link
Contributor

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 28, 2023
@cPu1 cPu1 removed the stale label Nov 28, 2023
@cPu1 cPu1 reopened this Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants