RE: 部署 k8s Cluster(上) — Kubernetes(5)

You are viewing a single comment's thread from:

部署 k8s Cluster(上) — Kubernetes(5)

in kubernetes •  7 years ago 

提示说加 --skip-preflight-checks ,然而 后面到了
[init] This often takes around a minute; or longer if the control plane images have to be pulled.
之后就失败了
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz' failed with error: Get http://localhost:10255/healthz: dial tcp [::1]:10255: getsockopt: connection refused.
搞了两天解决不了

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

初始部署肯定不能使用 --skip-preflight-checks。问题还是在下载image上。在 /etc/kubernetes/manifests/ 目录下有几个yaml文件,里面有 k8s需要的image的路径,可以先通过 docker pull 手工下载image,然后再运行 kubeadm init

这个我试过了,应该有4个
image,gcr.io/google_containers/kube-apiserver-amd64,
gcr.io/google_containers/kube-controller-manager-amd64,
gcr.io/google_containers/kube-scheduler-amd64,
gcr.io/google_containers/etcd-amd64:3.0.17

docker 全都pull了,最后还是超时失败

这我就不明白了,既然image都有了,就应该能正常init。用docker ps 能看到相应的容器吗?另外,确保手工下载的image版本与yaml中的一致

Loading...

同样的问题。折磨死了。

主要还是网络问题,可参考上面的手工下载image的方法

请问下这个问题怎么解决的啊?手动拉也失败了