Eric Greer

Kuberhealthy should not restart at all in normal conditions. Can you try running a `kubectl logs --previous ` shortly after you see a Kuberhealthy pod restart? The last entries should...

I am 50/50 on this one... If a pod in your cluster is able to spin up and run before it has a route to Kuberhealthy, then that is likely...

Happy to help there. What was going on in the Kuberhealthy pod logs during the bad behavior?

Master election is chosen by simply doing a `kubectl get pods` on Kuberhealthy and picking the instance that comes first in the listing. This has been consistent in all versions...

We also might want to change the health check in the helm chart to an `http` check instead a `tcp` one.

This may be best solved with a new check: #777

This is due to the DCO bot requiring your `git` commits to be signed. This is required by the CNCF to ensure that the committer's name can not be spoofed....

It is interesting that you don't use a capital `S` when signing commits and instead use a lowercase "sign off" that basically only puts something in the commit message. I...

I'm not opposed to this. It sounds like a useful check! You could develop this as your own repo and image, or you could suggest a pull request to this...

I wonder if this was because KinD was having NTP-like issues...