You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
✨ edge subnets: support Local Zones provisioning networks
Introducing the mechanism to query the zone information
from the subnet's AvailabilityZone, saving the ZoneType and
the ParentZoneName in the SubnetSpec, both for managed and unmanaged.
The ZoneType is used to group the zones from regular and the edge zones.
Regular zones are with type 'availability-zone', and the edge zones are
types 'local-zone' and 'wavelength-zone'.
The following statements are valid for edge subnets:
- private subnets supports egress traffic only using NAT Gateway in the
region.
- IPv6 subnets is not supported in edge zones
- subnet tags (kubernetes.io/role/*) for load balancer are not set in
edge subnets. Edge subnets should not be elected by CCM to create
service load balancers. Use ALB ingress instead.
✨ edge subnets/test: unit for subnets in Local Zones
Added unit tests to validate scenarios suing managed and unmanaged
subnets in AWS Local Zones, alongside new describe availability zones
API calls introduced in the subnet reconciliation loop.
✨ edge subnets/unit: fixes unit tests to describe zone calls
The edge subnets feature introduce a new AWS API call to describe zones,
DescribeAvailabilityZonesWithContext, to lookup zone attributes based in
the zone names in the reconciliator, and the create subnets.
The two new calls is required to support unmanaged subnets (BYO VPC),
where the method createSubnet() is not called.
There are some unit tests calling the create subnet flow, this change
add the mock calls for those calls.
0 commit comments