There's two ways to address this:
a) kuryr controller service manager restarts exited watches with a maximum reconnect attempts b) Implement /healthz/k8s API endpoint so a liveness probe can decide to restart the controller.
We probably need both approaches.
There's two ways to address this:
a) kuryr controller service manager restarts exited watches with a maximum reconnect attempts
b) Implement /healthz/k8s API endpoint so a liveness probe can decide to restart the controller.
We probably need both approaches.