kubeadm初始化异常

kubeadm初始化异常

1、提示错误

[kubelet-check] It seems like the kubelet isn't running or healthy.[kubelet-check] The HTTP call equal to 'curl -sSL failed with error: Get "dial tcp [::1]:10248: connect: connection refused.

解决方法：

[root@k8s-master ~]# cat /etc/docker/daemon.json{ "registry-mirrors": [" "exec-opts": ["native.cgroupdriver=systemd"]}

Docker​ 在默认情况下使用的 Cgroup Driver 为 ​​cgroupfs​​​，而kubernetes推荐使用systemd来代替cgroupfs，修改后重启docker服务

systemctl daemon-reloadsystemctl restart docker

2、提示错误

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 Kubernetes containers running in docker: - 'docker ps -a | grep kube | grep -v pause' Once you have found the failing container, you can inspect its logs with: - 'docker logs CONTAINERID'

使用journalctl -xeu kubelet查看错误日志

4月 01 10:00:59 k8s-master kubelet[10551]: I0401 10:00:59.651012 10551 cni.go:240] "Unable to update cni config" err="no networks found in /etc/cni/net.d"4月 01 10:00:59 k8s-master kubelet[10551]: E0401 10:00:59.737707 10551 kubelet.go:2422] "Error getting node" err="node \"k8s-master\" not found"4月 01 10:00:59 k8s-master kubelet[10551]: E0401 10:00:59.838451 10551 kubelet.go:2422] "Error getting node" err="node \"k8s-master\" not found"4月 01 10:00:59 k8s-master kubelet[10551]: E0401 10:00:59.939087 10551 kubelet.go:2422] "Error getting node" err="node \"k8s-master\" not found"4月 01 10:01:00 k8s-master kubelet[10551]: E0401 10:01:00.039405 10551 kubelet.go:2422] "Error getting node" err="node \"k8s-master\" not found"4月 01 10:01:00 k8s-master kubelet[10551]: E0401 10:01:00.140215 10551 kubelet.go:2422] "Error getting node" err="node \"k8s-master\" not found"4月 01 10:01:00 k8s-master kubelet[10551]: E0401 10:01:00.240983 10551 kubelet.go:2422] "Error getting node" err="node \"k8s-master\" not found"4月 01 10:01:00 k8s-master kubelet[10551]: E0401 10:01:00.247430 10551 eviction_manager.go:254] "Eviction manager: failed to get summary stats" err="failed to get node info: node \"k8s-master\" not found"4月 01 10:01:00 k8s-master kubelet[10551]: E0401 10:01:00.341871 10551 kubelet.go:2422] "Error getting node" err="node \"k8s-master\" not found"4月 01 10:01:00 k8s-master kubelet[10551]: E0401 10:01:00.443369 10551 kubelet.go:2422] "Error getting node" err="node \"k8s-master\" not found"4月 01 10:01:00 k8s-master kubelet[10551]: E0401 10:01:00.469960 10551 kubelet.go:2347] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized"

解决方法：

仔细检查kubeadm int时参数配置

kubeadm init --apiserver-advertise-address=192.168.201.128 --image-repository registry.aliyuncs.com/google_containers --kubernetes-version=v1.23.0 --service-cidr=10.96.0.0/12 --pod-network-cidr=10.244.0.0/16 --ignore-preflight-errors=all

发现--apiserver-advertise-address=192.168.201.128配置的IP不是master IP，修改正确的IP后，重新初始化（重新初始化之前需kubeadm reset，删除必要的目录）

版权声明：本文内容由网络用户投稿，版权归原作者所有，本站不拥有其著作权，亦不承担相应法律责任。如果您发现本站中有涉嫌抄袭或描述失实的内容，请联系我们jiasou666@gmail.com 处理，核实后本网站将在24小时内删除侵权内容。