the systemd couldn't start the kubelet on worker1 and 2 after using:
journalctl -u kubelet --since "1 minutes ago"
to see the logs on kubelet I found this:
failed to create kubelet: get remote runtime typed version failed: rpc error
after digging in the documentation I found here: https://kubernetes.io/docs/setup/production-environment/container-runtimes/
the following:
{
Note:
If you installed containerd from a package (for example, RPM or .deb), you may find that the CRI integration plugin is disabled by default.
You need CRI support enabled to use containerd with Kubernetes. _Make sure that cri is not included in thedisabledplugins list within /etc/containerd/config.toml; if you made changes to that file, also restart containerd.
}
so the solution:
sudo su
vi /etc/containerd/config.toml
and then comment the line for disabled plugins =[cri]
systemctl restart containerd
in the documentation they suggests to add other things to the file, but I found that removing the line of disabled plugins enough to make kubelet in active state..... I don't know why
I hope this will help others
the systemd couldn't start the kubelet on worker1 and 2 after using: journalctl -u kubelet --since "1 minutes ago" to see the logs on kubelet I found this: failed to create kubelet: get remote runtime typed version failed: rpc error after digging in the documentation I found here: https://kubernetes.io/docs/setup/production-environment/container-runtimes/ the following: { Note: If you installed containerd from a package (for example, RPM or .deb), you may find that the CRI integration plugin is disabled by default.
You need CRI support enabled to use containerd with Kubernetes. _Make sure that cri is not included in thedisabledplugins list within /etc/containerd/config.toml; if you made changes to that file, also restart containerd. }
so the solution: sudo su vi /etc/containerd/config.toml and then comment the line for disabled plugins =[cri] systemctl restart containerd in the documentation they suggests to add other things to the file, but I found that removing the line of disabled plugins enough to make kubelet in active state..... I don't know why I hope this will help others