-
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
Add support for wavelength zones #7107
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello antevens 👋 Thank you for opening a Pull Request in eksctl
project. The team will review the Pull Request and aim to respond within 1-10 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
Wow aws, good job |
Is this a feature that we can revisit (following completion of: #7202)? |
Allows adding nodegroups with wavelength zones.
Allows adding nodegroups with wavelength zones.
Description
Allows the use of wavelengh zones when adding nodegroups.
Fixes
Error: could not find public subnets: could not select subnets from subnet IDs (allSubnets=v1alpha5.AZSubnetMapping{"us-east-1b":v1alpha5.AZSubnetSpec{ID:"subnet-xxxxxxxxxxxxx", AZ:"us-east-1b", CIDR:(*ipnet.IPNet)(0xc000000000, CIDRIndex:0, OutpostARN:""}, "us-east-1f":v1alpha5.AZSubnetSpec{ID:"subnet-x", AZ:"us-east-1f", CIDR:(*ipnet.IPNet)(0x000000000), CIDRIndex:0, OutpostARN:""}} localZones=[]string(nil) subnets=[]string{"subnet-xxxxxxxxxxxxx"}): failed to select subnet subnet-xxxxxxxxxxxxx: error discovering zone types: expected zone type to be local or AZ; got wavelength-zone