Comment 2 for bug 1887438

I've reproduced the same behaviour (node stuck in "NotReady" status after forced reboot of active controller) in another lab.

I tracked it down to a bug in upstream Kubernetes, which in turn is being hit by a bug in upstream go.

I opened a Kubernetes issue to track the inclusion of the go fix into Kubernetes. The issue is at https://github.com/kubernetes/kubernetes/issues/93268

The bug report for go is at https://github.com/golang/go/issues/40213 and there are two patches currently in review to fix it.

We're still sorting out how we plan on dealing with this issue.