techiescamp / vagrant-kubeadm-kubernetes

Vagrantfile & Scripts to setup Kubernetes Cluster using Kubeadm for CKA, CKAD and CKS practice environment
https://devopscube.com/kubernetes-cluster-vagrant/
GNU General Public License v3.0
736 stars 714 forks source link

Why kube-apiserver container is trying to find containerID when it start by kubelet #36

Closed inkkim closed 7 months ago

inkkim commented 1 year ago

When I was accidently quit virtualbox VM and then I just boot up vagrant. kube-apiserver is trying to restart by kubelet.

root@master-node:/etc/kubernetes/manifests# crictl ps
CONTAINER           IMAGE                                                              CREATED             STATE               NAME                      ATTEMPT             POD ID              POD
0493210a252eb       deb04688c4a3559c313d0023133e3f95b69204f4bff4145265bc85e9672b77f3   49 seconds ago      Running             kube-apiserver            10                  73b158a97e9d0       kube-apiserver-master-node
5c3e62e7edeb4       655493523f6076092624c06fd5facf9541a9b3d54e6f3bf5a6e078ee7b1ba44f   39 minutes ago      Running             kube-scheduler            2                   d621927fbf32d       kube-scheduler-master-node
c054d83005832       e9c08e11b07f68c1805c49e4ce66e5a9e6b2d59f6f65041c113b635095a7ad8d   43 minutes ago      Running             kube-controller-manager   2                   717b0951ba423       kube-controller-manager-master-node
1a1287b77ccb5       46a6bb3c77ce01ed45ccef835bd95a08ec7ce09d3e2c4f63ed03c2c3b26b70fd   43 minutes ago      Running             kube-proxy                1                   6cf42b47cdf54       kube-proxy-s4h24
f2d57a250e409       fce326961ae2d51a5f726883fd59d2a8c2ccc3e45d3bb859882db58e422e59e7   43 minutes ago      Running             etcd                      2                   2d18ec2efa1dd       etcd-master-node

But the container has been printed out with this message.

root@master-node:/etc/kubernetes/manifests# crictl logs kube-apiserver-master-node
E0213 14:37:59.632422   33644 remote_runtime.go:415] "ContainerStatus from runtime service failed" err="rpc error: code = NotFound desc = could not find container \"kube-apiserver-master-node\": container with ID starting with kube-apiserver-master-node not found: ID does not exist" containerID="kube-apiserver-master-node"
FATA[0000] rpc error: code = NotFound desc = could not find container "kube-apiserver-master-node": container with ID starting with kube-apiserver-master-node not found: ID does not exist

Why kube-apiserver is trying to find containerID which is named kube-apiserver-master-node?

Here is my environment.

Does anyone has same experience or any solution?