Skip to content

CORS-4315: enable primary IPv6 when infrastructure ipFamily is DualStackIPv6Primary#171

Open
tthvo wants to merge 1 commit intoopenshift:mainfrom
tthvo:CORS-4315
Open

CORS-4315: enable primary IPv6 when infrastructure ipFamily is DualStackIPv6Primary#171
tthvo wants to merge 1 commit intoopenshift:mainfrom
tthvo:CORS-4315

Conversation

@tthvo
Copy link
Member

@tthvo tthvo commented Jan 21, 2026

Description

For dual-stack IPv6-primary clusters, instances must have a primary IPv6 address on their primary ENI to registery with the IPv6 Target Groups of API and Ingress load balancers. See AWS docs

Notes

This assumes that the containing subnet is dual-stack (has both IPv4 and IPv6 CIDRs) since we are requesting an IPv6 address for the instance. The subnets, created by installer/capa, will be dual-stack and will auto-assign an IPv6 address on launch.

…imary

For dual-stack IPv6-primary clusters, instances must have a primary IPv6
address on their primary ENI to registery with the IPv6 Target Groups of API
and Ingress load balancers.
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 21, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 21, 2026

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

Details

In response to this:

Description

For dual-stack IPv6-primary clusters, instances must have a primary IPv6 address on their primary ENI to registery with the IPv6 Target Groups of API and Ingress load balancers. See AWS docs

Notes

This assumes that the containing subnet is dual-stack (has both IPv4 and IPv6 CIDRs) since we are requesting an IPv6 address for the instance. The subnets, created by installer/capa, will be dual-stack and will auto-assign an IPv6 address on launch.

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 openshift-ci bot requested review from nrb and theobarberbany January 21, 2026 23:17
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 21, 2026

[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 joelspeed 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:

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

@tthvo
Copy link
Member Author

tthvo commented Jan 21, 2026

/hold

This is a preview of the idea to adjust MAPA to react based on the infra status ipFamily.

Important: We have not finalized on which direction to go yet (i.e. auto react or explicit MAPA machine field) 👀

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 21, 2026
@tthvo
Copy link
Member Author

tthvo commented Jan 21, 2026

/cc @damdo @patrickdillon @sadasu

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 22, 2026

@tthvo: all tests passed!

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants