CORS-4072: [Draft] Dual stack support for AWS #9930

tthvo · 2025-09-09T01:42:10Z

Important

A rough draft of installer changes required to support dual-stack environment on AWS.

This PR is only for previewing the changes and experimenting with upstream CAPA PR. I will close this and open another PR with finalized sets of changes.

This PR also includes commits (message starting with hack: ) to "imitate" CCM, MAPI, and Cluster Ingress Operator to create necessary resources for cluster ingress (i.e. NLB, Route53 records, Security Groups, etc) and enable Ipv6 primary (if applicable). These commits are to be removed, assuming dual-stack is supported in operators later on.

This depends on upstream CAPA PR: kubernetes-sigs/cluster-api-provider-aws#5603

How to install

Below is the details of how to reproduce the installation.

$ export OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE=quay.io/thvo/origin-release:v4.22.0-preview-ds
$ export AWS_PROFILE=<profile-admin>
$ ./openshift-install create cluster --dir=.

Custom release image

Custom release image: quay.io/thvo/origin-release:v4.22.0-preview-ds

This includes the following operator changes:

CORS-4209: ensure NodeIPFamilies field is kept as-is after transforming cluster-cloud-controller-manager-operator#426
CORS-4220: pass dualstack cluster cidrs as an comma-separated list argument cluster-kube-controller-manager-operator#889
CORS-4208: set default KUBELET_NODE_IPS for dualstack nodes machine-config-operator#5384
cluster-network-operator: tthvo/cluster-network-operator@617e05f (quick test without feature gates)

For the cluster-network-operator, we have the open PR here with feature gate checking: openshift/cluster-network-operator/pull/2804

Install Config

Use the below install-config snippet to configure networking and AWS platform.

Note: machineNetwork does not contain IPv6 CIDR as it is unknown at install time (i.e. will be patched later when infra is ready). The cluster network and service network contain ULA IPv6 CIDR.

IPv4 Primary:

networking:
  clusterNetwork:
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  - cidr: fd01::/48
    hostPrefix: 64
  machineNetwork:
  - cidr: 10.0.0.0/16
  networkType: OVNKubernetes
  serviceNetwork:
  - 172.30.0.0/16
  - fd02::/112
platform:
  aws:
    region: us-east-1
    ipFamily: DualStackIPv4Primary
featureSet: TechPreviewNoUpgrade

IPv6 Primary:

networking:
  clusterNetwork:
  - cidr: fd01::/48
    hostPrefix: 64
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  machineNetwork:
  - cidr: 10.0.0.0/16
  networkType: OVNKubernetes
  serviceNetwork:
  - fd02::/112
  - 172.30.0.0/16
platform:
  aws:
    region: us-east-1
    ipFamily: DualStackIPv6Primary
featureSet: TechPreviewNoUpgrade

Important notes: [IPv6-primary only] The ingress operator will be stuck as health check on targets are failing because the k8s Service for ingress routers only have IPv6 cluster IP. The hacks only configures the ingress LB target group as IPv4, thus the connection cannot switch to IPv6 when travelling internally.

~~You must edit the that service openshift-ingress/router-nodeport-default to set its ipFamilyPolicy to PreferDualStack. For example:~~

$ kubectl -n openshift-ingress patch svc router-nodeport-default \
    -p '{"spec":{"ipFamilyPolicy":"PreferDualStack"}}'

Updated: There is a new commit to "hack" enable IPv6 primary on ec2 instances for cluster nodes. So, above step is no longer needed. The Target Group for dual-stack IPv6 primary is now also IPv6.

Installer binary

The installer binary can be built normally from these commits (i.e. capa is vendored from my fork). So, just:

./hack/build.sh

/hold
/label platform/aws

openshift-ci-robot · 2025-09-09T01:42:16Z

@tthvo: This pull request references CORS-4072 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "4.21." or "openshift-4.21.", but it targets "openshift-4.20" instead.

Details

In response to this:

A rough draft of installer changes required to support dual-stack environment on AWS.

Important

This PR is only for previewing the changes and supposed to be closed after done experimenting. I will open another PR with finalized sets of changes.

Notes

Commits with message hack: are changes to "imitate" CCM and Cluster Ingress Operator to create necessary resources for cluster ingress (i.e. NLB, Route53 records, Security Groups, etc).

This depends on upstream CAPA PR: ✨ IPv6 support for self-managed clusters kubernetes-sigs/cluster-api-provider-aws#5603

/hold
/label platform/aws

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

tthvo · 2025-09-09T01:45:49Z

/cc @sadasu @barbacbd @rna-afk

tthvo · 2025-09-09T01:48:23Z

/cc @mtulio

Just rough hacks but in case you are interested :D

openshift-ci-robot · 2025-09-09T04:08:17Z

@tthvo: This pull request references CORS-4072 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "4.21." or "openshift-4.21.", but it targets "openshift-4.20" instead.

Details

In response to this:

A rough draft of installer changes required to support dual-stack environment on AWS.

This PR is only for previewing the changes and experimenting with upstream CAPA PR. I will close this and open another PR with finalized sets of changes.

How to install

Below is the details of how to reproduce the installation.
$ export OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE=quay.io/thvo/origin-release:v4.21.0-preview
$ export AWS_PROFILE=<profile-admin>
$ ./openshift-install create cluster --dir=.
Custom release image

Custom release image: quay.io/thvo/origin-release:v4.21.0-preview.

This includes the following operator changes:

cluster-cloud-controller-manager-operator: tthvo/cluster-cloud-controller-manager-operator@d1a105d

cluster-network-operator: tthvo/cluster-network-operator@617e05f

kube-controller-manager-operator: tthvo/cluster-kube-controller-manager-operator@3658370

Install Config

Use the below install-config snippet to configure networking and AWS platform.
networking:
 clusterNetwork:
 - cidr: 10.128.0.0/14
   hostPrefix: 23
 - cidr: fd01::/48
   hostPrefix: 64
 machineNetwork:
 - cidr: 10.0.0.0/16
 networkType: OVNKubernetes
 serviceNetwork:
 - 172.30.0.0/16
 - fd02::/112
platform:
 aws:
   region: us-east-1
   infraStack: DualStack
Note that machineNetwork does not contain IPv6 CIDR as it is unknown at install time (i.e. will be patched later when infra is ready). The cluster network and service network contain ULA IPv6 CIDR.

Installer binary

It looks the installer binary can be built from these commits despite a reference to my local CAPA fork. So, just:
./hack/build.sh
Important

Commits with message hack: are changes to "imitate" CCM and Cluster Ingress Operator to create necessary resources for cluster ingress (i.e. NLB, Route53 records, Security Groups, etc). See log with prefix INFO CCM: .

This depends on upstream CAPA PR: ✨ IPv6 support for self-managed clusters kubernetes-sigs/cluster-api-provider-aws#5603 (not finalized yet).

/hold
/label platform/aws

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

data/data/install.openshift.io_installconfigs.yaml

pkg/asset/manifests/aws/zones.go

pkg/types/defaults/installconfig.go

pkg/infrastructure/aws/clusterapi/ignition.go

pkg/infrastructure/aws/clusterapi/aws.go

pkg/asset/tls/apiserver.go

tthvo · 2025-09-10T01:29:56Z

/test e2e-aws-default-config e2e-aws-ovn-shared-vpc-custom-security-groups

tthvo · 2025-10-21T19:27:02Z

/retitle CORS-4072: [Draft] Dual stack support for AWS

This PR is for experimenting and collecting info about what changes are needed. I will separate the commits into smaller PRs :D

PTAL 🙏 All reviews and nitpicks are appreciated!

tthvo · 2025-10-31T06:46:40Z

The rebase is to stay on top of upstream/main and remove the hack for MCO (9fa264d) as MCO should handle setting the approriate 0.0.0.0/:: to --node-ip argument of kubelet. See PR description more details 😁 🙏

tthvo · 2025-11-11T05:41:22Z

I rebuilt another release image: quay.io/thvo/origin-release:v4.21.0-preview-1. This includes the changes for openshift/cluster-network-operator#2804 instead of my own hack tthvo/cluster-network-operator@617e05f.

If you'd like to use the new custom release image, you need to set the techpreview feature set:

featureSet: TechPreviewNoUpgrade

openshift-ci · 2026-01-13T21:46:43Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign sadasu for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-ci-robot · 2026-01-13T21:51:12Z

@tthvo: This pull request references CORS-4072 which is a valid jira issue.

Details

In response to this:

Important

A rough draft of installer changes required to support dual-stack environment on AWS.

This PR is only for previewing the changes and experimenting with upstream CAPA PR. I will close this and open another PR with finalized sets of changes.

This PR also includes commits (message starting with hack: ) to "imitate" CCM, MAPI, and Cluster Ingress Operator to create necessary resources for cluster ingress (i.e. NLB, Route53 records, Security Groups, etc) and enable Ipv6 primary (if applicable). These commits are to be removed, assuming dual-stack is supported in operators later on.

This depends on upstream CAPA PR: kubernetes-sigs/cluster-api-provider-aws#5603

How to install

Below is the details of how to reproduce the installation.
$ export OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE=quay.io/thvo/origin-release:v4.22.0-preview-ds
$ export AWS_PROFILE=<profile-admin>
$ ./openshift-install create cluster --dir=.
Custom release image

Custom release image: quay.io/thvo/origin-release:v4.22.0-preview-ds

This includes the following operator changes:

CORS-4209: ensure NodeIPFamilies field is kept as-is after transforming cluster-cloud-controller-manager-operator#426

CORS-4220: pass dualstack cluster cidrs as an comma-separated list argument cluster-kube-controller-manager-operator#889

CORS-4208: set default KUBELET_NODE_IPS for dualstack nodes machine-config-operator#5384

cluster-network-operator: tthvo/cluster-network-operator@617e05f (quick test without feature gates)

For the cluster-network-operator, we have the open PR here with feature gate checking: openshift/cluster-network-operator/pull/2804

Install Config

Use the below install-config snippet to configure networking and AWS platform.

Note: machineNetwork does not contain IPv6 CIDR as it is unknown at install time (i.e. will be patched later when infra is ready). The cluster network and service network contain ULA IPv6 CIDR.

IPv4 Primary:
networking:
 clusterNetwork:
 - cidr: 10.128.0.0/14
   hostPrefix: 23
 - cidr: fd01::/48
   hostPrefix: 64
 machineNetwork:
 - cidr: 10.0.0.0/16
 networkType: OVNKubernetes
 serviceNetwork:
 - 172.30.0.0/16
 - fd02::/112
platform:
 aws:
   region: us-east-1
   ipFamily: DualStackIPv4Primary
IPv6 Primary:
networking:
 clusterNetwork:
 - cidr: fd01::/48
   hostPrefix: 64
 - cidr: 10.128.0.0/14
   hostPrefix: 23
 machineNetwork:
 - cidr: 10.0.0.0/16
 networkType: OVNKubernetes
 serviceNetwork:
 - fd02::/112
 - 172.30.0.0/16
platform:
 aws:
   region: us-east-1
   ipFamily: DualStackIPv6Primary
Important notes: [IPv6-primary only] The ingress operator will be stuck as health check on targets are failing because the k8s Service for ingress routers only have IPv6 cluster IP. The hacks only configures the ingress LB target group as IPv4, thus the connection cannot switch to IPv6 when travelling internally.

~~You must edit the that service openshift-ingress/router-nodeport-default to set its ipFamilyPolicy to PreferDualStack. For example:~~
$ kubectl -n openshift-ingress patch svc router-nodeport-default \
   -p '{"spec":{"ipFamilyPolicy":"PreferDualStack"}}'
Updated: There is a new commit to "hack" enable IPv6 primary on ec2 instances for cluster nodes. So, above step is no longer needed. The Target Group for dual-stack IPv6 primary is now also IPv6.

Installer binary

The installer binary can be built normally from these commits (i.e. capa is vendored from my fork). So, just:
./hack/build.sh
/hold
/label platform/aws

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci-robot · 2026-01-13T21:51:47Z

@tthvo: This pull request references CORS-4072 which is a valid jira issue.

Details

In response to this:

Important

A rough draft of installer changes required to support dual-stack environment on AWS.

This PR is only for previewing the changes and experimenting with upstream CAPA PR. I will close this and open another PR with finalized sets of changes.

This PR also includes commits (message starting with hack: ) to "imitate" CCM, MAPI, and Cluster Ingress Operator to create necessary resources for cluster ingress (i.e. NLB, Route53 records, Security Groups, etc) and enable Ipv6 primary (if applicable). These commits are to be removed, assuming dual-stack is supported in operators later on.

This depends on upstream CAPA PR: kubernetes-sigs/cluster-api-provider-aws#5603

How to install

Below is the details of how to reproduce the installation.
$ export OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE=quay.io/thvo/origin-release:v4.22.0-preview-ds
$ export AWS_PROFILE=<profile-admin>
$ ./openshift-install create cluster --dir=.
Custom release image

Custom release image: quay.io/thvo/origin-release:v4.22.0-preview-ds

This includes the following operator changes:

CORS-4209: ensure NodeIPFamilies field is kept as-is after transforming cluster-cloud-controller-manager-operator#426

CORS-4220: pass dualstack cluster cidrs as an comma-separated list argument cluster-kube-controller-manager-operator#889

CORS-4208: set default KUBELET_NODE_IPS for dualstack nodes machine-config-operator#5384

cluster-network-operator: tthvo/cluster-network-operator@617e05f (quick test without feature gates)

For the cluster-network-operator, we have the open PR here with feature gate checking: openshift/cluster-network-operator/pull/2804

Install Config

Use the below install-config snippet to configure networking and AWS platform.

Note: machineNetwork does not contain IPv6 CIDR as it is unknown at install time (i.e. will be patched later when infra is ready). The cluster network and service network contain ULA IPv6 CIDR.

IPv4 Primary:
networking:
 clusterNetwork:
 - cidr: 10.128.0.0/14
   hostPrefix: 23
 - cidr: fd01::/48
   hostPrefix: 64
 machineNetwork:
 - cidr: 10.0.0.0/16
 networkType: OVNKubernetes
 serviceNetwork:
 - 172.30.0.0/16
 - fd02::/112
platform:
 aws:
   region: us-east-1
   ipFamily: DualStackIPv4Primary
featureSet: TechPreviewNoUpgrade
IPv6 Primary:
networking:
 clusterNetwork:
 - cidr: fd01::/48
   hostPrefix: 64
 - cidr: 10.128.0.0/14
   hostPrefix: 23
 machineNetwork:
 - cidr: 10.0.0.0/16
 networkType: OVNKubernetes
 serviceNetwork:
 - fd02::/112
 - 172.30.0.0/16
platform:
 aws:
   region: us-east-1
   ipFamily: DualStackIPv6Primary
featureSet: TechPreviewNoUpgrade
Important notes: [IPv6-primary only] The ingress operator will be stuck as health check on targets are failing because the k8s Service for ingress routers only have IPv6 cluster IP. The hacks only configures the ingress LB target group as IPv4, thus the connection cannot switch to IPv6 when travelling internally.

~~You must edit the that service openshift-ingress/router-nodeport-default to set its ipFamilyPolicy to PreferDualStack. For example:~~
$ kubectl -n openshift-ingress patch svc router-nodeport-default \
   -p '{"spec":{"ipFamilyPolicy":"PreferDualStack"}}'
Updated: There is a new commit to "hack" enable IPv6 primary on ec2 instances for cluster nodes. So, above step is no longer needed. The Target Group for dual-stack IPv6 primary is now also IPv6.

Installer binary

The installer binary can be built normally from these commits (i.e. capa is vendored from my fork). So, just:
./hack/build.sh
/hold
/label platform/aws

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

tthvo · 2026-01-13T21:55:29Z

The PR is rebased on top of main with latest capa IPv6 PR changes; and adjusted to match #10207 implementation for the install-config field. I also rebuilt a new custom release image based on 4.22.0-ec.0: quay.io/thvo/origin-release:v4.22.0-preview-ds.

Both dual-stack Ipv4 primary and dual-stack IPv6 primary install (using install-config in the PR description) should proceed to the end successfully (and "seamlessly") 😄

patrickdillon

Looks good on first pass

pkg/types/aws/platform.go

pkg/asset/machines/clusterapi.go

pkg/asset/manifests/aws/cluster.go

pkg/infrastructure/aws/clusterapi/aws.go

Based on install-config input, update AWSPlatformStatus's IPFamily field within the Infrastructure manifest. Update unit tests to reflect this new field.

…-network-server The commit ensures all service networks are considered (i.e. that is all IP families) when generating the certificate kube-apiserver-service-network-server.

The installconfig in the cluster-config ConfigMap needs to have the Ipv6 CIDR of the VPC in the case of full IPI.

This applies to dualstack installation only. IPv4-primary: IPv4 Target Group IPv6-primary: Ipv6 Target Group

FIXME: we should use the VPC CIDR as the source CIDRs. But the IPv6 cidr is not yet knowned at install time. We should edit the awscluster after infraReady to add the VPC IPv6 CIDR as source instead.

FIXME: CCM and in-cluster MAPI/CAPI needs to handle this

openshift-ci · 2026-01-15T01:36:16Z

@tthvo: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-azure-ovn-resourcegroup	`49c133a`	link	false	`/test e2e-azure-ovn-resourcegroup`
ci/prow/e2e-aws-custom-dns-techpreview	`49c133a`	link	false	`/test e2e-aws-custom-dns-techpreview`
ci/prow/okd-scos-e2e-aws-ovn	`44dfeb3`	link	false	`/test okd-scos-e2e-aws-ovn`
ci/prow/e2e-azure-ovn	`0985757`	link	true	`/test e2e-azure-ovn`
ci/prow/e2e-aws-ovn-heterogeneous	`0985757`	link	false	`/test e2e-aws-ovn-heterogeneous`
ci/prow/e2e-gcp-custom-dns	`0985757`	link	false	`/test e2e-gcp-custom-dns`
ci/prow/e2e-azurestack	`0985757`	link	false	`/test e2e-azurestack`

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

tthvo · 2026-01-27T02:50:39Z

I have started on splitting the changes in this PR into smaller individual PRs for easy review. But this PR is still kept open for quick testing.

openshift-merge-robot · 2026-01-27T02:50:48Z

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 9, 2025

openshift-ci bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. platform/aws labels Sep 9, 2025

openshift-ci bot requested review from jhixson74 and patrickdillon September 9, 2025 01:44

openshift-ci bot requested review from barbacbd, rna-afk and sadasu September 9, 2025 01:45

openshift-ci bot requested a review from mtulio September 9, 2025 01:48

tthvo force-pushed the CORS-4072 branch from f3bd838 to 7bb3478 Compare September 9, 2025 03:50

tthvo force-pushed the CORS-4072 branch 3 times, most recently from 0e37a46 to 537f4d0 Compare September 9, 2025 07:17

barbacbd reviewed Sep 9, 2025

View reviewed changes

openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 13, 2025

tthvo force-pushed the CORS-4072 branch from 537f4d0 to 9d16f01 Compare September 15, 2025 17:23

openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 15, 2025

tthvo force-pushed the CORS-4072 branch from 9d16f01 to 49c133a Compare September 15, 2025 22:11

openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 21, 2025

tthvo force-pushed the CORS-4072 branch from 49c133a to bb54f97 Compare October 21, 2025 19:18

openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 21, 2025

openshift-ci bot changed the title ~~CORS-4072: [WIP] Dual stack support for AWS~~ CORS-4072: [Draft] Dual stack support for AWS Oct 21, 2025

tthvo force-pushed the CORS-4072 branch 2 times, most recently from d5cef48 to dac6b81 Compare October 21, 2025 21:03

openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 11, 2025

tthvo mentioned this pull request Nov 11, 2025

CORS-4180: Allow AWS and Azure as platforms that support dual-stack on Day-0 openshift/cluster-network-operator#2804

Merged

tthvo force-pushed the CORS-4072 branch from 44dfeb3 to f6f9116 Compare January 13, 2026 21:45

openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 13, 2026

patrickdillon mentioned this pull request Jan 14, 2026

CORS-4075, CORS-4113: Install-config and Infra manifest updates for DualStack for AWS and Azure #10207

Merged

patrickdillon reviewed Jan 14, 2026

View reviewed changes

pkg/types/aws/platform.go Outdated Show resolved Hide resolved

pkg/asset/machines/clusterapi.go Outdated Show resolved Hide resolved

pkg/asset/manifests/aws/cluster.go Outdated Show resolved Hide resolved

pkg/infrastructure/aws/clusterapi/aws.go Outdated Show resolved Hide resolved

tthvo and others added 11 commits January 14, 2026 12:35

do-not-merge: pointing aws provider to fork version

06deab5

installconfig: define a ipFamily installconfig field

185c1c3

Update Infrastructure CR's IPFamily field

2ac8b50

Based on install-config input, update AWSPlatformStatus's IPFamily field within the Infrastructure manifest. Update unit tests to reflect this new field.

capi: provide IPv6 block to CAPA

2601721

route53: create AAAA records for api lb

ba9d886

tls: ensure all ip families are considered for kube-apiserver-service…

53b597c

…-network-server The commit ensures all service networks are considered (i.e. that is all IP families) when generating the certificate kube-apiserver-service-network-server.

ignition: add vpc ipv6 cidr to installconfig if needed

61754ea

The installconfig in the cluster-config ConfigMap needs to have the Ipv6 CIDR of the VPC in the case of full IPI.

api-lb: configure IP family for API LB target group

447eff1

This applies to dualstack installation only. IPv4-primary: IPv4 Target Group IPv6-primary: Ipv6 Target Group

nodeport-sg: allow all ipv4 and ipv6 nodeport ingress rule

9728b69

FIXME: we should use the VPC CIDR as the source CIDRs. But the IPv6 cidr is not yet knowned at install time. We should edit the awscluster after infraReady to add the VPC IPv6 CIDR as source instead.

hack: create the nlb and route53 records for default router

e579788

hack: wait for worker nodes and register targets with ingress LB

0985757

FIXME: CCM and in-cluster MAPI/CAPI needs to handle this

tthvo force-pushed the CORS-4072 branch from f6f9116 to 0985757 Compare January 14, 2026 21:19

patrickdillon mentioned this pull request Jan 22, 2026

CORS-4294: Adding dualstack presubmit job openshift/release#73270

Open

tthvo mentioned this pull request Jan 27, 2026

CORS-4328: configure AWS CCM NodeIPFamilies for dual-stack support #10257

Open

openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 27, 2026

CORS-4072: [Draft] Dual stack support for AWS #9930

Are you sure you want to change the base?

CORS-4072: [Draft] Dual stack support for AWS #9930

Uh oh!

Conversation

tthvo commented Sep 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Important

How to install

Custom release image

Install Config

Installer binary

Uh oh!

openshift-ci-robot commented Sep 9, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

tthvo commented Sep 9, 2025

Uh oh!

tthvo commented Sep 9, 2025

Uh oh!

openshift-ci-robot commented Sep 9, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

How to install

Custom release image

Install Config

Installer binary

Important

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

tthvo commented Sep 10, 2025

Uh oh!

tthvo commented Oct 21, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

tthvo commented Oct 31, 2025

Uh oh!

tthvo commented Nov 11, 2025

Uh oh!

openshift-ci bot commented Jan 13, 2026

Uh oh!

openshift-ci-robot commented Jan 13, 2026 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Important

How to install

Custom release image

Install Config

Installer binary

Uh oh!

openshift-ci-robot commented Jan 13, 2026 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Important

How to install

Custom release image

Install Config

Installer binary

Uh oh!

tthvo commented Jan 13, 2026

Uh oh!

patrickdillon left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

openshift-ci bot commented Jan 15, 2026

Uh oh!

tthvo commented Jan 27, 2026

Uh oh!

openshift-merge-robot commented Jan 27, 2026

Uh oh!

Reviewers

Assignees

Labels

tthvo commented Sep 9, 2025 •

edited

Loading

openshift-ci-robot commented Sep 9, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Sep 9, 2025 •

edited by openshift-ci bot

Loading

tthvo commented Oct 21, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Jan 13, 2026 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Jan 13, 2026 •

edited by openshift-ci bot

Loading