Close kepler pod with Error if watcher failed

[jochen-schuettler]

When we startup k8s with all pods, it takes some time until everything is up and runnning. It's possible that pods aren't answering correctly during kepler startup. We encountered a watcher failure. We think it might be best to stop the kepler pod with Error in that case and let it be restarted by k8s.

I0417 10:26:43.810341       1 watcher.go:66] Using in cluster k8s config
W0417 10:27:13.844549       1 reflector.go:535] pkg/kubernetes/watcher.go:128: failed to list *v1.Pod: Get "https://10.96.0.1:443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0": dial tcp 10.96.0.1:443: i/o timeout
I0417 10:27:13.860302       1 trace.go:236] Trace[698411094]: "Reflector ListAndWatch" name:pkg/kubernetes/watcher.go:128 (17-Apr-2024 10:26:43.814) (total time: 30045ms):
Trace[698411094]: ---"Objects listed" error:Get "https://10.96.0.1:443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0": dial tcp 10.96.0.1:443: i/o timeout 30027ms (10:27:13.841)
Trace[698411094]: [30.045382367s] [30.045382367s] END
E0417 10:27:13.869780       1 reflector.go:147] pkg/kubernetes/watcher.go:128: Failed to watch *v1.Pod: failed to list *v1.Pod: Get "https://10.96.0.1:443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0": dial tcp 10.96.0.1:443: i/o timeout
I0417 10:27:15.220039       1 watcher.go:137] k8s APIserver watcher was started

I0418 09:47:48.947929       1 watcher.go:66] Using in cluster k8s config
I0418 09:47:49.049013       1 watcher.go:137] k8s APIserver watcher was started