Currently when a watch ends we always dump the config and application caches. There's a more graceful way to resume a watch using resource versions. As long as Kubernetes continues to track changes for the specific resource version we shouldn't need to rebuild the caches.
Currently when a watch ends we always dump the config and application caches. There's a more graceful way to resume a watch using resource versions. As long as Kubernetes continues to track changes for the specific resource version we shouldn't need to rebuild the caches.