Join GitHub today
Add kubelet health checking #160
Added notes about missing golang documentation strings. Though this is looking good!
Yes, but it should be quite rare. The path would be that an update finished but then the end state didn't work as it should. Generally speaking
Human or operator intervention. If the node is degraded it will most likely be re-provisioned. It can be possible for a human to do node surgery to force the node to be compliant, but that is a pattern we are trying to avoid.
[APPROVALNOTIFIER] This PR is APPROVED
The full list of commands accepted by this bot can be found here.
The pull request process is described here