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
The applier currently stops trying to process new scheduling requests while trying to write back the result of a reconciliation. This leads to a deadlock where the buffer is never emptied because we're busy trying to fill it.
Thanks to @moustafab for reporting the issue and contributing a workaround.
Possible solution
Explicitly try to empty the buffer during writeback
Current and expected behavior
See #925 for more details.
The applier currently stops trying to process new scheduling requests while trying to write back the result of a reconciliation. This leads to a deadlock where the buffer is never emptied because we're busy trying to fill it.
Thanks to @moustafab for reporting the issue and contributing a workaround.
Possible solution
Additional context
No response
Environment
This is a runtime issue, independent of K8s version
Configuration and features
kube 0.73.1
Affected crates
kube-runtime
Would you like to work on fixing this bug?
yes
The text was updated successfully, but these errors were encountered: