XML

Word

Printable

Epic Name:
Installer support for AWS dual-stack clusters
Epic Status:
In Progress
Activity Type:
Product / Portfolio Work
Parent Link:
OCPSTRAT-886Dual-stack enablement for OCP on AWS
Hierarchy Progress Bar:

38% To Do, 33% In Progress, 29% Done
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Color Status:
Green
Status Summary:
Hide

Date: 17/02/2026

Status: Green

Note:

We have identified installer pieces that are required to bring up a healthy dualstack cluster. See https://github.com/openshift/installer/pull/9930.

The draft PR is being split into smaller manageable pieces.

The largest piece will be to configure CAPI/CAPI manifest to enable dualstack network infrastructure. Currently, we are waiting on upstream CAPA PR https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/5603.
Show
Date: 17/02/2026 Status: Green Note: We have identified installer pieces that are required to bring up a healthy dualstack cluster. See https://github.com/openshift/installer/pull/9930 . The draft PR is being split into smaller manageable pieces. The largest piece will be to configure CAPI/CAPI manifest to enable dualstack network infrastructure. Currently, we are waiting on upstream CAPA PR https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/5603 .
Size:
None

Epic Goal

Add support with the OpenShift Installer to bring up dual-stack clusters on AWS.

Why is this important?

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

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.

N/A

N/A

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>