Common kubectl errors after restart

sh
kubectl config current-context
 
kubectl config view --minify

sh
#
ps -ef | grep kube-apiserver
 
#
sudo ss -tulpn | grep :6443

sh
# check kubelet running
sudo systemctl status kubelet
 
# Check kubelet logs
sudo journalctl -u kubelet -n 100 | grep -i "kube-apiserver"

sh
# check if containerd is running
sudo systemctl status containerd
 
sudo systemctl restart containerd
 
# identify if kube-apiserver is failing
sudo crictl pods | grep kube-apiserver
 
#
$ sudo crictl logs <POD_ID>
WARN[0000] Config "/etc/crictl.yaml" does not exist, trying next: "/usr/bin/crictl.yaml"
WARN[0000] runtime connect using default endpoints: [unix:///run/containerd/containerd.sock unix:///run/crio/crio.sock unix:///var/run/cri-dockerd.sock]. As the default settings are now deprecated, you should set the endpoint instead.
E0830 10:22:16.632738    5628 log.go:32] "ContainerStatus from runtime service failed" err="rpc error: code = NotFound desc = an error occurred when try to find container \"d48fe70335c54\": not found" containerID="d48fe70335c54"
FATA[0000] rpc error: code = NotFound desc = an error occurred when try to find container "d48fe70335c54": not found