kube-dns 和 weave-net 未启动

Question

我正在按照 http://kubernetes.io/docs/getting-started-guides/kubeadm/ 上的说明在 Raspberry Pi 3 上的 Ubuntu 16 上部署 Kubernetes 1.4。 master 启动并且 minion 加入没问题但是当我添加编织时 kubedns 不会启动。这是 pods:

k8s@k8s-master:~$ kubectl get pods --all-namespaces
NAMESPACE     NAME                                 READY     STATUS              RESTARTS   AGE
kube-system   etcd-k8s-master                      1/1       Running             1          23h
kube-system   kube-apiserver-k8s-master            1/1       Running             3          23h
kube-system   kube-controller-manager-k8s-master   1/1       Running             1          23h
kube-system   kube-discovery-1943570393-ci2m9      1/1       Running             1          23h
kube-system   kube-dns-4291873140-ia4y8            0/3       ContainerCreating   0          23h
kube-system   kube-proxy-arm-nfvvy                 1/1       Running             0          1h
kube-system   kube-proxy-arm-tcnta                 1/1       Running             1          23h
kube-system   kube-scheduler-k8s-master            1/1       Running             1          23h
kube-system   weave-net-4gqd1                      0/2       CrashLoopBackOff    54         1h
kube-system   weave-net-l758i                      0/2       CrashLoopBackOff    44         1h

事件日志没有显示任何内容。获取 kube-dns 的日志也没有得到任何东西。

我可以做些什么来调试？

Answer 1

kube-dns 网络启动后才会启动。

查看每台计算机上的 kubelet 日志，了解有关导致 CrashLoopBackoff 的崩溃的详细信息。

~~您是如何为 Weave Net 获取 ARM 映像的？ DockerHub 上的 weaveworks/weave-kube 镜像仅为 x64 构建。~~

编辑：正如@pidster所说Weave Net now supports ARM

Answer 2

更新：正如 Bryan 所指出的，Flannel 不再是唯一的覆盖网络。

注意 kubeadm install documentation:

中的这两个提示

~~Flannel 是 arm 唯一的网络覆盖支持~~

~~If you are on another architecture than amd64, you should use the flannel overlay network as described in the multi-platform section~~

使用Flannel时，需要进行kubectl init --por-network-cidr=10.244.0.0/16

Note: this will autodetect the network interface to advertise the master on as the interface with the default gateway. If you want to use a different interface, specify --api-advertise-addresses= argument to kubeadm init. If you want to use flannel as the pod network, specify --pod-network-cidr=10.244.0.0/16 if you’re using the daemonset manifest below. However, please note that this is not required for any other networks besides Flannel.

您可能还想检查 my automated step-by-step installation for Raspberry Pi 3 with Ansible，因为 DNS 没有问题并且可能也适用于 Ubuntu 16：

NAMESPACE     NAME                                           READY     STATUS    RESTARTS   AGE
default       busybox-894550917-7vj3z                        1/1       Running   0          15h
default       busybox-894550917-p9vnl                        1/1       Running   1          3d
default       gogs-3464422143-cf5wb                          1/1       Running   0          16h
kube-system   dummy-2501624643-pxmgz                         1/1       Running   2          3d
kube-system   etcd-master.cluster.local                      1/1       Running   2          3d
kube-system   kube-apiserver-master.cluster.local            1/1       Running   2          3d
kube-system   kube-controller-manager-master.cluster.local   1/1       Running   2          3d
kube-system   kube-discovery-1659614412-vrhv4                1/1       Running   2          3d
kube-system   kube-dns-4211557627-kpsj4                      4/4       Running   8          3d
kube-system   kube-flannel-ds-d1bgg                          2/2       Running   6          3d
kube-system   kube-flannel-ds-fcp4b                          2/2       Running   6          3d
kube-system   kube-flannel-ds-n7p3m                          2/2       Running   6          3d
kube-system   kube-flannel-ds-tn7nd                          2/2       Running   6          3d
kube-system   kube-flannel-ds-vpk4w                          2/2       Running   6          3d
kube-system   kube-proxy-5nmtn                               1/1       Running   2          3d
kube-system   kube-proxy-gq7bz                               1/1       Running   2          3d
kube-system   kube-proxy-lkkgm                               1/1       Running   2          3d
kube-system   kube-proxy-mlh3v                               1/1       Running   1          3d
kube-system   kube-proxy-sg8n8                               1/1       Running   2          3d
kube-system   kube-scheduler-master.cluster.local            1/1       Running   2          3d
kube-system   kubernetes-dashboard-3507263287-h9q33          1/1       Running   2          3d

kube-dns 和 weave-net 未启动

kube-dns and weave-net not starting

kubernetes

weave

raspberry-pi3

kube-dns