-
Notifications
You must be signed in to change notification settings - Fork 4
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
Fix multiple load balancers in one tenant #62
Conversation
Hi @jan-walther. Thanks for your PR. I'm waiting for a kubermatic 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. |
2746f37
to
aebe59a
Compare
/ok-to-test |
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.
Thank you @jan-walther for the contribution. Left a comment and can you please fix the failing CI jobs/tests.
Signed-off-by: Jan Walther <jan.walther@sva.de>
aebe59a
to
68a3ca3
Compare
/retest |
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.
/approve
I'll move ahead and merge this PR. I can take a look at #62 (comment) in a follow-up PR.
LGTM label has been added. Git tree hash: 7ea4dd3e2866dbd22c17260e1fd49af9aa5a9d30
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahmedwaleedmalik 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 this PR does / why we need it:
This PR fixes having multiple load balancer for a single tenant. If you
continue
after checking if theaddressesMap
, no second cluster and listener(s) will be created leaving only a single service on the load balancer.Which issue(s) this PR fixes:
Fixes #
What type of PR is this?
/kind bug
Special notes for your reviewer:
This blocks a customer, a fast review would be appreciated.
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: