K8S集群kubelet启动异常 kubelet.go:2267] node “node“ not found

最新推荐文章于 2024-06-25 17:55:25 发布

沉年半

最新推荐文章于 2024-06-25 17:55:25 发布

阅读量9.3w

点赞数 2

CC 4.0 BY-SA版权

文章标签： kubernetes 运维

本文链接：https://blog.csdn.net/weixin_40614231/article/details/109307323

在部署openyurt时遇到k8s节点加入集群时kubelet异常，表现为'node 'node' not found'。通过检查kubelet状态、对比集群配置，发现kubeconfig路径错误，由于之前转换集群操作导致kubelet配置被修改。通过vim编辑配置文件，修复kubeconfig路径，然后成功加入集群。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

背景：这个问题是我在尝试部署openyurt的时候遇到的，同一个问题因人而异，具体排查请看自己的log，此篇仅供参考！

问题

最近在尝试部署openyurt，需要先准备一个搭好的k8s集群来yurtctl convert，但是在node节点join集群的时候总是遇到问题：

[root@node ~]# kubeadm join xxxxxxxx
[preflight] Running pre-flight checks
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[kubelet-start] Downloading configuration for the kubelet from the "kubelet-config-1.16" ConfigMap in the kube-system namespace
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Activating the kubelet service
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
[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'
error execution phase kubelet-start: timed out waiting for the condition
To see the stack trace of this error execute with --v=5 or higher

显然，kube