Skip to content

Conversation

@tthvo
Copy link
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.

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.
@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
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
Member Author

tthvo commented Jan 27, 2026

/label platform/aws

@tthvo
Copy link
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
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 27, 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 rvanderp3 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 27, 2026

/cc @yunjiang29

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

openshift-ci bot commented Jan 27, 2026

@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-aws-ovn-edge-zones d1f15d1 link false /test e2e-aws-ovn-edge-zones
ci/prow/e2e-aws-ovn-heterogeneous d1f15d1 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.

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

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. platform/aws

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants