Steven Hawkins

This is currently the expected behavior - network level errors are not handled by the exceptionHandler. That is only for unexpected exceptions with running the Reflector. This would be an...

> If I skip creating a proxy and start an informer, it will fail to connect to the server as well but it will do invoke retryAfterExcetion which is not...

> I do not see any other flags that might help identify connection loss. Is running is expected to be true until the informer is stopped. isWatching is not quite...

Separated off https://github.com/fabric8io/kubernetes-client/issues/7167 - we can report the underlying Watch state in the isWatching method. However allowing the ExceptionHandler to weigh in is a bigger change - it's highly related...

The desire here is to have the exeception handler apply to reconnect attempts, it still does not.

Thinking about this more in light of #7365, I think we can just effectively remove the Watcher.reconnecting logic, and everything will work as expected. The only small downside is that...

> I have looked into this issue and but the issue is happening in other class. https://github.com/fabric8io/kubernetes-client/issues/6747 That is happening for a different reason - that is a localized executor....

> What's the resolution for this issue? There is none. I don't see a way to reproduce this other than there being a violation of the memory model on your...

@vmuzikar I did a GHA run and ran the original reproducer test successfully against 2.4.240.

Looks like this already happened in https://github.com/quarkusio/quarkus/commit/723ab13d2a9e4166d16cec7c473871376875ea7d