-
Notifications
You must be signed in to change notification settings - Fork 831
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
do not act on resources that have deletion timestamp set #2782
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Mon Dec 14 17:05:47 UTC 2020 impatient try |
Mon Dec 14 17:06:00 UTC 2020 impatient try |
/test this |
/test integration |
Mon Dec 14 17:09:46 UTC 2020 impatient try |
Mon Dec 14 17:09:54 UTC 2020 impatient try |
Mon Dec 14 18:14:34 UTC 2020 impatient try |
Mon Dec 14 18:14:44 UTC 2020 impatient try |
/test integration |
/test notebooks |
Tue Dec 15 10:43:12 UTC 2020 impatient try |
Tue Dec 15 10:44:46 UTC 2020 impatient try |
/test notebooks |
Tue Dec 15 14:43:13 UTC 2020 impatient try |
Tue Dec 15 14:43:30 UTC 2020 impatient try |
Tue Dec 15 14:43:58 UTC 2020 impatient try |
Tue Dec 15 14:44:13 UTC 2020 impatient try |
Tue Dec 15 14:44:32 UTC 2020 impatient try |
Tue Dec 15 18:24:46 UTC 2020 impatient try |
Tue Dec 15 18:24:53 UTC 2020 impatient try |
Tue Dec 15 18:40:42 UTC 2020 impatient try |
Tue Dec 15 18:40:54 UTC 2020 impatient try |
/test notebooks |
/test integration |
Meant to trigger integration (stopped the notebooks pipeline) |
Tue Dec 15 19:40:42 UTC 2020 impatient try |
@RafalSkolasinski: The following test failed, say
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 jenkins-x/lighthouse repository. I understand the commands that are listed here. |
/test integration |
Wed Dec 16 08:36:27 UTC 2020 impatient try |
Wed Dec 16 09:58:02 UTC 2020 impatient try |
Wed Dec 16 09:58:07 UTC 2020 impatient try |
What this PR does / why we need it:
This avoids having
Operator
re-creating Pods (and other resources) that are being removed throughforeground
deletion mechanism, e.g. ArgoCD-powered gitops.Which issue(s) this PR fixes:
Closes #2781
Special notes for your reviewer:
For reference, this is how it is done in kfserving.
This is important because in foreground deletion resource is still available through the API while it is being deleted.
If we don't stop early on the
reconcile
logic we would be recreating the pods that are being deleted.Logic here differs from one in kfserving as we do not use finalizers.
Does this PR introduce a user-facing change?: