Skip to content

CORS-4142: ensure lbType is NLB when dual-stack is configured #10256

Merged
openshift-merge-bot[bot] merged 2 commits intoopenshift:mainfrom
tthvo:CORS-4142-lbType
Feb 7, 2026
Merged

CORS-4142: ensure lbType is NLB when dual-stack is configured #10256
openshift-merge-bot[bot] merged 2 commits intoopenshift:mainfrom
tthvo:CORS-4142-lbType

Conversation

@tthvo
Copy link
Copy Markdown
Member

@tthvo tthvo commented Jan 27, 2026

This PR adds validation to ensure platform.aws.lbType is NLB when dual-stack networking is configured on AWS. AWS does not support dual-stack for Classic load balancers.

Additionally, if lbType is left empty and ipFamily is set to dual-stack values, the installer will default lbType to NLB. I guess this is a nice user experience so that they have to remember configuring load balancer type.

This is part 1 of CORS-4142. Part 2 will focus on populating ingress and default ingress-controller manifests.

@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 27, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Jan 27, 2026

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

Details

In response to this:

This PR adds validation to ensure platform.aws.lbType is NLB when dual-stack networking is configured on AWS. AWS does not support dual-stack for Classic load balancers.

Additionally, if lbType is left empty and ipFamily is set to dual-stack values, the installer will default lbType to NLB. I guess this is a nice user experience so that they have to remember configuring load balancer type.

This is part 1 of CORS-4142. Part 2 will focus on populating ingress and default ingress-controller manifests.

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
Copy link
Copy Markdown
Member Author

tthvo commented Jan 27, 2026

/label platform/aws

@tthvo
Copy link
Copy Markdown
Member Author

tthvo commented Jan 27, 2026

/cc @sadasu @barbacbd

@openshift-ci openshift-ci bot requested review from barbacbd and sadasu January 27, 2026 01:18
@tthvo
Copy link
Copy Markdown
Member Author

tthvo commented Jan 27, 2026

/cc @yunjiang29

@openshift-ci openshift-ci bot requested a review from yunjiang29 January 27, 2026 02:47
Copy link
Copy Markdown
Contributor

@sadasu sadasu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 Nit inline to explain the default Ingress load balancer values and its new connection to the ipFamily field.

tthvo added 2 commits February 5, 2026 10:11
This commit adds validation to ensure platform.aws.lbType is NLB when
dual-stack networking is configured on AWS. AWS does not support
dual-stack for Classic load balancers.

Additionally, if lbType is left empty and ipFamily is set to dual-stack
values, the installer will default lbType to NLB.
@patrickdillon
Copy link
Copy Markdown
Contributor

/lgtm
/approve
/verified by unit

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 6, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@patrickdillon: This PR has been marked as verified by unit.

Details

In response to this:

/lgtm
/approve
/verified by unit

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 added the lgtm Indicates that a PR is ready to be merged. label Feb 6, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Feb 6, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon

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

The pull request process is described 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 6, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Feb 7, 2026

@tthvo: The following test 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-aws-ovn-heterogeneous 6382d3e link false /test e2e-aws-ovn-heterogeneous

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
Copy link
Copy Markdown
Member Author

tthvo commented Feb 7, 2026

/retest-required

@openshift-merge-bot openshift-merge-bot bot merged commit 870432a into openshift:main Feb 7, 2026
24 of 25 checks passed
@tthvo tthvo deleted the CORS-4142-lbType branch February 7, 2026 22:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. platform/aws verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants