Epic Goal

To allow dualstack install on AWS:

• Evaluate current CAPA support for dualstack unmanaged clusters (managed EKS clusters seem to have complete IPv6 support).
• Open upstream CAPA PR(s) to bridge gaps in support.

Note: The phrase "dualstack" here means AWS dualstack network infrastructure (i.e. VPC, subnets, NLBs, etc). This is distinct from Kubernetes dualtstack, where pods and services are assigned IP addresses from both IP families.

Why is this important?

• Allowing choice between ipv4 & ipv6 introduces more user opportunities, particularly to meet federal requirements.

Scenarios

Installing a dualstack kubernetes cluster on a dualstack networking infrastructure. There are 2 sub-scenarios:

• Dualstack IPv6 primary: IPv6 addressing is preferred with IPv4 addressing being optional for fallback.
• Dualstack IPv4 primary: vice versa.

Acceptance Criteria

• Dualstack network infrastructure can be provisioned.
• CI - MUST be running successfully with tests automated

Dependencies (internal and external)

N/A

Previous Work (Optional):

N/A

Open questions:

N/A

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>