Orphan pod xxxxxx found, but volume paths are still present on disk is shown in logs, Kubelet may be required a restart.
Access into the node.
docker psand check the kublet status, meanwhile, there should no any running K8S relative containers.
Stop kubelet; run
docker stop kubelet.
Rename the original kubelet working folder; run
sudo mv /var/lib/kubelet /var/lib/kubelet.del.
Start kubelet; run
docker start kubelet; kubelet working folder should be re-generated.
Once kubelet is started and work ab, there should be some running K8S containers; verify it with