-
Notifications
You must be signed in to change notification settings - Fork 306
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
Ensure ingress cleanup when finalizer exists #1144
Conversation
Hi @skmatti. Thanks for your PR. I'm waiting for a kubernetes 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. |
e9fe044
to
562a684
Compare
/ok-to-test |
// 1. Ingress update for class change. | ||
// 2. Ingress cleanup failed and re-queued. | ||
// 3. Finalizer remove failed and re-queued. | ||
if common.HasFinalizer(curIng.ObjectMeta) { |
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.
Is it possible that a super old version of ingress controller (without finalizer) gets directly updated to this version?
Would it basically skip all syncs for existing ingress?
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.
This will be released to 1.17 only and both 1.15, 1.16 versions have finalizers enabled. So, the above case may be highly unlikely
/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.
/lgtm
/approve
/assign
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: freehan, skmatti 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 |
Cherrypick #1144 [Ensure ingress cleanup when finalizer exists] into release-1.9
No description provided.