kubeadm init：couldn‘t initialize a Kubernetes cluster

问题：

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, e.g. docker.
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’
  couldn’t initialize a Kubernetes cluster

排查一：

1、检查是否开了代理，如有，关掉代理重新init。
查看：env | grep -i proxy

2、关闭
gedit /etc/enviroment 去掉相关代理http_proxy、https_proxy

还有~/.bashrc /etc/profile中的代理，然后
source ~/.bashrc
source /etc/profile
使修改生效

查看：env | grep -i proxy

如果还存在代理，运行：

unset http_proxy

unset https_proxy

完美解决。

若还存在，参考如下链接删掉代理：
ubuntu取消http_proxy设置

排查二：
参阅如下链接：
https://www.jianshu.com/p/cb6d564d9a59

https://zhangkesheng.github.io/2017/11/16/Kubernetes-Install/