The fabric8 built-in watch support is similar to a retrywatcher in the go client - until http gone it will maintain the watch automatically. Because the watch is restarted at an exact resourceVersion, there are no duplicate add events.

The next option is to use an informer, but in some circumstances there may be a concern about the size of an informer cache. Either we need to offer additional cache customization features - similar to #3472 - or introduce a further enhanced watch construct that goes beyond the retry to handle http gone. Under the covers this would look like an informer that caches only the resource key and version, but the user would still use the Watcher interface.