-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Labels
Comments
7 tasks
Thanks @cPu1! Would there be any test cases that the reviewers could use when reviewing the PR? |
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. |
This issue was closed because it has been stalled for 5 days with no activity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What were you trying to accomplish?
In trying to launch a self-managed node group in Local Zones, I used
What happened?
eksctl failed to create the node group because of the following error:
The error message reads got wavelength-zone, however the subnet in reference (subnet-0fbfc2d5a0c70cc05) is 100% a Local Zone (see below):
When recreating this cluster from an AWS Account only allow-listed to Local Zones but not Wavelength Zones, no such error occurs.
Versions
The text was updated successfully, but these errors were encountered: