-
Notifications
You must be signed in to change notification settings - Fork 219
[release-4.2] Bug 1769882: Ensures LB service finalizer is removed #325
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
[release-4.2] Bug 1769882: Ensures LB service finalizer is removed #325
Conversation
|
@openshift-cherrypick-robot: This pull request references Bugzilla bug 1766141, which is invalid:
Comment DetailsIn response to this:
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. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: openshift-cherrypick-robot The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/retitle [release-4.2] Bug 1769882: Ensures LB service finalizer is removed |
|
@openshift-cherrypick-robot: This pull request references Bugzilla bug 1769882, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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. |
| // lbServiceCleanUpFinalizer is a finalizer attached to any service that has type=LoadBalancer. | ||
| // Upon deletion of the service, the actual deletion of the resource will be blocked until | ||
| // this finalizer is removed. | ||
| lbServiceCleanUpFinalizer = "service.kubernetes.io/load-balancer-cleanup" |
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.
We cannot use this in OpenShift 4.2 or earlier because the finalizer is new in Kubernetes 1.16:
Specifically, if a Service has type LoadBalancer, the service controller will attach a finalizer named service.kubernetes.io/load-balancer-cleanup. The finalizer will only be removed after the load balancer resource is cleaned up. This prevents dangling load balancer resources even in corner cases such as the service controller crashing.
This feature is beta and enabled by default since Kubernetes v1.16. You can also enable it in v1.15 (alpha) via the feature gate ServiceLoadBalancerFinalizer.
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.
Can we refactor master to use existence checks before back porting?
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.
Can we refactor master to use existence checks before back porting?
@danehans although I phrased this as a question, I guess it's more of a statement that the refactor is necessary because the information to support the current approach simply does not exist in 4.1 and 4.2 clusters
|
This can't be automatically backported. /close |
|
@ironcladlou: Closed this PR. DetailsIn response to this:
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. |
This is an automated cherry-pick of #320
/assign danehans