使用kubeadm安装kubernetes集群,报:[kubelet-check] Initial timeout of 40s passed

识趣 发表于: 2022-07-21   最后更新时间: 2022-07-21 11:07:53   2,425 游览

我使用kubeadm安装kubernetes集群,一直不成功。

错误详情:

[kubelet-check] Initial timeout of 40s passed.

Unfortunately, an error has occurred:
        timed out waiting for the condition

This error is likely caused by:
        - The kubelet is not running
        - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
        - 'systemctl status kubelet'
        - 'journalctl -xeu kubelet'

Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all running Kubernetes containers by using crictl:
        - 'crictl --runtime-endpoint unix:///var/run/cri-dockerd.sock ps -a | grep kube | grep -v pause'
        Once you have found the failing container, you can inspect its logs with:
        - 'crictl --runtime-endpoint unix:///var/run/cri-dockerd.sock logs CONTAINERID'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher

请问我该如何解决?

发表于 2022-07-21
添加评论

怎么解决的呢 跪求

你可以使用

systemctl status kubelet

journalctl -xeu kubelet

查看具体报错的原因。

另外,kubernetes master组件可能在容器运行时启动时崩溃。

要查看故障原因,使用容器运行时 CLI 列出所有容器。下面是一个如何使用 crictl 列出所有正在运行的 Kubernetes 容器的示例:

crictl --runtime-endpoint unix:///var/run/cri-dockerd.sock ps -a | grep kube | grep -v pause

找到故障容器后,可以使用以下命令检查其日志:

crictl --runtime-endpoint unix:///var/run/cri-dockerd.sock logs CONTAINERID
你的答案

查看kubeadm相关的其他问题或提一个您自己的问题