Perform automatic retries for 410s during watches

[JacobHenner]

At this time, when a watch expires (with a 410 Gone) the watcher returns an "error" event to the caller. Instead of returning a raw error event, it should attempt to resume the watch (as it would after a timeout). If that fails, it should raise an exception.

A similar change has been incorporated into the kubernetes-client/python library: https://github.com/kubernetes-client/python-base/pull/133

See also:

• https://github.com/tomplus/kubernetes_asyncio/issues/135
• https://github.com/tomplus/kubernetes_asyncio/issues/134

[JacobHenner]

I'm not sure I still agree with the change proposed originally. I'm going to think about it some more, and will update this issue once I have a better idea of what the desired behavior is (see discussion in the see also links).

[remram44]

I ran into this. I am trying to fix the bug, but it is hard to validate a fix since it takes a long time before a 410 gets returned by Kubernetes. An automatic retry in kubernetes-asyncio would be appreciated, especially since the sync kubernetes client has it.