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
If a handler deletes the object being handled, Kopf will try to patch its status after the handler as usually, and will fail, since the object does not exist anymore.
The same happens if the object is deleted too quickly, while the handler is running.
Previously, this was prevented by always having a finalizer before any handling. Since #24, the finalizer is added only when there are non-optional delete handlers, and skipped otherwise. So, it is now possible that the object is deleted while we handling it.
Types of Changes
Bug fix (non-breaking change which fixes an issue)
Review
Tests
Documentation
The text was updated successfully, but these errors were encountered:
Ignore errors when patching an object that was removed too quickly, during the handling cycle or inside of the handlers.
Description
If a handler deletes the object being handled, Kopf will try to patch its status after the handler as usually, and will fail, since the object does not exist anymore.
The same happens if the object is deleted too quickly, while the handler is running.
Previously, this was prevented by always having a finalizer before any handling. Since #24, the finalizer is added only when there are non-optional delete handlers, and skipped otherwise. So, it is now possible that the object is deleted while we handling it.
Types of Changes
Review
The text was updated successfully, but these errors were encountered: