User Story:

Currently, the installer provides the AZs for CAPA to create the subnets by specifying awscluster.spec.network.subnets, where the subnet AZs define the AZs to use (more details here). This is necessary as in region us-east-1, we want to skip AZ us-east-1e.

However, when enabling IPv6 support, we can't specify the subnets directly as we don't know the subnet IPv6 CIDRs. Thus, we need a way to define the AZ list as ids or names.

Note: Upstream CAPA needs to support this setting.

Acceptance Criteria:

Description of criteria:

• Ability to define the AZs to use directly (i.e. a list of AZ ids/names).

(optional) Out of Scope:

Detail about what is specifically not being delivered in the story

Engineering Details:

• Upstream issue: https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/4333 
• Corresponding PR: https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/4950 (just awaiting a final approval)

This requires/does not require a design proposal.
This requires/does not require a feature gate.