#minor Remove unnecessary sleep before each watch cycle #326
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During my work with this project I've discovered that some DELETE k8s events are skipped for unknown reason.
After some digging, I've managed to discover that if a DELETE event is sent while sidecar in its 5 seconds sleep between watch cycles, this event is simply gets skipped. There's no one to receive it. And after ERROR_THROTTLE_SLEEP seconds watch cycle starts, receives all modified and added k8s resources, but it doesn't get any events about deleted stuff.
And sidecar lacks a reconciliation loop to handle deleted resources based on received list of resources.
By shifting sleep throttle to only exceptions case we should manage to catch most of the DELETE events.