-
Notifications
You must be signed in to change notification settings - Fork 280
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: fix bugs regarding multiple slbs #4289
fix: fix bugs regarding multiple slbs #4289
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nilo19 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 |
/test pull-cloud-provider-azure-e2e-ccm-vmss-multi-slb-capz |
2 similar comments
/test pull-cloud-provider-azure-e2e-ccm-vmss-multi-slb-capz |
/test pull-cloud-provider-azure-e2e-ccm-vmss-multi-slb-capz |
/retest |
/test pull-cloud-provider-azure-e2e-ccm-vmss-ip-lb-capz |
/retest |
0b26912
to
6af392a
Compare
/test pull-cloud-provider-azure-e2e-ccm-vmss-multi-slb-capz |
6af392a
to
8283c19
Compare
/test pull-cloud-provider-azure-e2e-ccm-vmss-multi-slb-capz |
/test pull-cloud-provider-azure-e2e-ccm-vmssflex-capz |
fix: return the existing lb it if the lb exists without creating a new lb when the service was moved to the lb fix: should skip non-existent lb when arranging nodes chore: fix multi-slb e2e test
8283c19
to
bda7c54
Compare
/test pull-cloud-provider-azure-e2e-ccm-vmss-multi-slb-capz |
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.
/lgtm
What type of PR is this?
/kind bug
What this PR does / why we need it:
getServiceLoadBalancer
should return the existing lb object instead of creating a new one when a service is being moved from another lb to this one.existingLBs
should be updated when the lb is updated to prevent potential etag mismatches inEnsureHostsInPool
.Which issue(s) this PR fixes:
Fixes #
Related: 4013
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: