1、安装kubernetes1.22.2，master节点安装成功
2、主节点进程情况正常
3、master阶段docker ps情况正常
4、kubectl get node和cs情况正常
kubectl get node
NAME STATUS ROLES AGE VERSION
centos8-1 Ready control-plane,master 4d11h v1.22.2
[root@centos8-1 kubernetes]#
kubectl get cs
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME STATUS MESSAGE ERROR
scheduler Healthy ok
etcd-0 Healthy {"health":"true","reason":""}
controller-manager Healthy ok
[root@centos8-1 kubernetes]#
问题：
在node节点执行kubeadm join失败
[kubelet-start] Starting the kubelet
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp [::1]:10248: connect: connection refused.
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'
timed out waiting for the condition
error execution phase kubelet-start
通过journalctl查看日志
12月 04 23:17:55 CentOS8-2 systemd[1]: kubelet.service: Service RestartSec=10s expired, scheduling restart.
12月 04 23:17:55 CentOS8-2 systemd[1]: kubelet.service: Scheduled restart job, restart counter is at 499.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Automatic restarting of the unit kubelet.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
12月 04 23:17:55 CentOS8-2 systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
-- Subject: kubelet.service 单元已结束停止操作
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- kubelet.service 单元已结束停止操作。
12月 04 23:17:55 CentOS8-2 systemd[1]: Started kubelet: The Kubernetes Node Agent.
-- Subject: kubelet.service 单元已结束启动
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- kubelet.service 单元已结束启动。
--
-- 启动结果为“done”。
12月 04 23:17:55 CentOS8-2 kubelet[16072]: Flag --network-plugin has been deprecated, will be removed along with dockershim.
12月 04 23:17:55 CentOS8-2 kubelet[16072]: Flag --network-plugin has been deprecated, will be removed along with dockershim.
12月 04 23:17:55 CentOS8-2 kubelet[16072]: I1204 23:17:55.100323 16072 server.go:440] "Kubelet version" kubeletVersion="v1.22.2"
12月 04 23:17:55 CentOS8-2 kubelet[16072]: I1204 23:17:55.100679 16072 server.go:600] "Standalone mode, no API client"
12月 04 23:17:55 CentOS8-2 kubelet[16072]: E1204 23:17:55.100850 16072 server.go:294] "Failed to run kubelet" err="failed to run Kubelet: no client provided, cannot use webhook authentication"
12月 04 23:17:55 CentOS8-2 systemd[1]: kubelet.service: Main process exited, code=exited, status=1/FAILURE
12月 04 23:17:55 CentOS8-2 systemd[1]: kubelet.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit kubelet.service has entered the 'failed' state with result 'exit-code'.
[root@CentOS8-2 kubernetes]#
刚开始学习k8s，卡在kubeadm join，没有头绪，还请指导，万分感谢
