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
Break out of loop when finalizer is found #82053
Conversation
/assign @MrHohn |
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
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fejta, tedyu 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 |
/priority backlog |
/hold per release-managers discussion, holding low-priority, non-milestone-targeted PRs in order to free merge pool bandwidth for 1.16-targeted PRs feel free to unhold once there are no lgtm+approve+green 1.16-targeted PRs remaining. |
/hold cancel |
/test pull-kubernetes-integration |
/test pull-kubernetes-node-e2e |
/test pull-kubernetes-kubemark-e2e-gce-big |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
In WaitForServiceUpdatedWithFinalizer, when the LoadBalancerCleanupFinalizer is found, we can come out of the loop.
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: