Haoming Zhang

To work around this problem, you can either: 1) implement your own `ListerWatcher` to replace the default one in ` SharedInformerFactory`; or 2) explicitly set a non-0 timeout (for example...

@brendandburns @yue9944882 Could you help to triage? Thanks!

@GitHub-Yann Did you find a solution? We hit a similar issue after API server overwhelmed and restarted: some informers are still working while one of them stop getting updates.

Hi @GitHub-Yann, I recently found a potential bug: https://github.com/kubernetes-client/java/issues/2183#issue-1181153693 Base on my local experiments, once that bug is resolved, the watch call will have client-side timeout every 5-10mins, and will...