-
Notifications
You must be signed in to change notification settings - Fork 316
feat(l4): Add support for enabling L4 NetLB Regional Backend Services by default #2967
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 08volt The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Hi @08volt. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
|
/ok-to-test |
|
/retest |
| }, | ||
| { | ||
| desc: "Should detect RBS by default", | ||
| isRBSDefault: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about other testcases? We need to check if this doesn't modify existing Target pool LBs. I think it might be easier to add expectRBSServiceWithDefault to existing testcases and run with flag "true" and "false"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added those cases and added the check for ForwardingRule legacy in the controller code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
6b43126 to
7c64a95
Compare
7c64a95 to
eaf3a7a
Compare
|
PR needs rebase. 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. |
feat(l4): Enable L4 NetLB Regional Backend Services by default
This change introduces a feature flag
--enable-l4-netlb-rbs-by-defaultto enable the use of L4 NetLB Regional Backend Services (RBS) by default for newly created L4 NetLB services, instead of relying on CCM as default implementation.Changes:
EnableL4NetLBRBSByDefaultfield toControllerContextConfiginpkg/context/context.go.--enable-l4-netlb-rbs-by-defaultboolean flag inpkg/flags/flags.go, defaulting tofalse.L4NetLBControllerinpkg/l4lb/l4netlbcontroller.goto use theEnableL4NetLBRBSByDefaultsetting from the context.isRBSBasedServicelogic to returntrueif theenableRBSDefaultflag is set, in addition to existing checks (annotations, finalizers, existing FR).pkg/l4lb/l4netlbcontroller_test.goto test the new default behavior.This change allows clusters to default to using the more modern RBS for L4 NetLBs, while still allowing individual services to use the legacy instance-based backend services if explicitly setting the LoadBalancerClass spec in the Service.
#L4NetLB #RBS