kubeadm init --config kubeadm-init.yaml --ignore-preflight-errors=all --v=6

使用公网ip无法初始化集群，私网ip倒是可以，但是仅限于单节点集群，不符合课程的要求

I0404 18:24:11.941949    2408 round_trippers.go:454] GET https://114.116.237.81:6443/healthz?timeout=10s  in 10000 milliseconds
I0404 18:24:22.442318    2408 round_trippers.go:454] GET https://114.116.237.81:6443/healthz?timeout=10s  in 10000 milliseconds
I0404 18:24:32.941977    2408 round_trippers.go:454] GET https://114.116.237.81:6443/healthz?timeout=10s  in 10001 milliseconds
I0404 18:24:43.441703    2408 round_trippers.go:454] GET https://114.116.237.81:6443/healthz?timeout=10s  in 10000 milliseconds
I0404 18:24:53.941628    2408 round_trippers.go:454] GET https://114.116.237.81:6443/healthz?timeout=10s  in 10000 milliseconds
I0404 18:25:04.441679    2408 round_trippers.go:454] GET https://114.116.237.81:6443/healthz?timeout=10s  in 10000 milliseconds

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'

按照提示都执行了，提示说kubelet找不到master。
按照网上的一些方法试了感觉没效果。