You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 14, 2020. It is now read-only.
Technically: The finalizers removal criteria have changed from
"when done && reason == DELETE" to "when no delays returned"
(see 7adba02).
But the delays were not returned for multi-step deletion (2+ handlers),
so the finalizers were removed immediately after the 1st on-deletion
handler, and the 2nd and further on-deletion handlers were not invoked.
Now, with a delay of 0 for not yet finished (but not delayed) handlers,
it will not be considered as "done", which will prevent the deletion
of finalizers until really all handlers are finished either way.
See zalando-incubator#356
Long story short
If you use kopf.timer ans kopf create/update on the same resource, "kubectl delete" hangs.
Description
kubectl delete logconfigs xxx
^-- this command hangs.
Logs say that the delete function has run with success:
the kubectl command does not return.
The code snippet to reproduce the issue
The full output of the command that failed
Environment
Python packages installed
The text was updated successfully, but these errors were encountered: