kubeadm:主节点永不就绪 [英] kubeadm: master node never ready

问题描述

我正在关注博客文章，以使用kubeadm设置kubernetes集群.因此，我有一个使用网桥网络创建的Virtualbox，只需按照说明进行操作即可.

I'm following a blog post to setup a kubernetes cluster with kubeadm. So I have a Virtualbox created with bridge network and simply followed the instructions.

起初我只是做kubeadm init，但是没有用(大师NotReady).因此，我认为较旧的版本可能会更好.

I initially just did kubeadm init and it didn't work (master NotReady). So I figured maybe an older version might work better.

所以我做到了

kubeadm init --kubernetes-version v1.6.2

完成非常快.但是kubeadm get nodes总是返回:

It finished quite quickly. But kubeadm get nodes always returns:

master    NotReady   4m        v1.6.3

我检查了已下载的docker镜像，它们是这样的:

I checked the docker images that was downloaded and they're like this:

gcr.io/google_containers/kube-proxy-amd64                v1.6.2              7a1b61b8f5d4        4 weeks ago         109.2 MB
gcr.io/google_containers/kube-controller-manager-amd64   v1.6.2              c7ad09fe3b82        4 weeks ago         132.7 MB
gcr.io/google_containers/kube-apiserver-amd64            v1.6.2              e14b1d5ee474        4 weeks ago         150.5 MB
gcr.io/google_containers/kube-scheduler-amd64            v1.6.2              b55f2a2481b9        4 weeks ago         76.76 MB
gcr.io/google_containers/etcd-amd64                      3.0.17              243830dae7dd        12 weeks ago        168.9 MB
gcr.io/google_containers/pause-amd64                     3.0                 99e59f495ffa        12 months ago       746.9 kB

和docker ps的输出表明以下容器正在使用pause

and output of docker ps shows that the following containers are using pause

k8s_POD_kube-scheduler-master_kube-system_e4c05f51e4e89758e2fb58eb9c457e66_2
k8s_POD_kube-controller-manager-master_kube-system_14cceb4cae4afafe5d2872cedc46b03f_2
k8s_POD_etcd-master_kube-system_7075157cfd4524dbe0951e00a8e3129e_2
k8s_POD_kube-apiserver-master_kube-system_bd46883c0ce86694060fb2924470cfa7_2

我有点困惑:

1. 在什么情况下主节点会进入Ready状态?

为什么我要求的版本(和docker images标签)与kubeadm报告的版本之间有区别?

Why the difference between the version I asked (and the docker images tag) and the version reported by kubeadm?

推荐答案

您似乎没有设置网络叠加层.例如，如果是绒布，就应该是这样

It looks like you did not set a Network Overlay. For example, if for flanneld it would be like this

 kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
 kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/k8s-manifests/kube-flannel-rbac.yml

此后，您的节点应更改为就绪".

After this, your node should change to Ready.

这篇关于kubeadm:主节点永不就绪的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！