This might appear in vSphere with Tanzu / TKGS or TKGm clusters.
This is caused by the node reporting Ready:False or Unknown state to the TKG Control Plane nodes. The best way to identify what is causing the failure is to run the 'kubectl get nodes
' command from the TKC's control plane context. Then describe the node that shows NotReady status to identify why it is reporting NotReady.
Depending on the cause of the NotReady status, the node might be corrected with manual intervention, or it may require recreation depending on the failure state. Review KB 379071 for details on why a worker node might enter NotReady state.