-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
improve validation conditions for MetalLB BGP Peers #8568
improve validation conditions for MetalLB BGP Peers #8568
Conversation
Hi @kakkotetsu. Thanks for your PR. I'm waiting for a kubernetes-sigs 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/test-infra repository. |
looks good to improve the check. /cc @cristicalin |
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.
Thanks for taking care of this @kakkotetsu
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cristicalin, kakkotetsu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
When I replace MetalLB speaker by calico Service LoadBalancer IP advertisement,
metallb_peers
is NOT mandatory. (docs / MetalLB / BGP Mode)And when
metallb_peers
is mandatory(metallb_protocol
is bgp &&metallb_speaker_enabled
is true), it is also better to make sure themetallb_peers
is not empty({}
).Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: