kube-dns和weave-net无法启动

绒布是对arm的唯一网络覆盖支持 如果您使用的不是amd64架构，则应使用多平台部分中所述的法兰绒覆盖网络使用Flannel时，您需要进行kubectl初始化--por-network-cidr = 10.244.0.0/16 注意:这将自动检测网络接口以通告 master作为与默认网关的接口.如果你想 使用不同的界面，指定 --api-advertise-addresses = kubeadm初始化的参数. 如果要将法兰绒用作Pod网络，请指定 --pod-network-cidr = 10.244.0.0/16(如果您使用的是以下守护程序清单).但是，请注意，任何 除了绒布以外的其他网络.您可能还想查看我为使用Ansible的Raspberry Pi 3自动进行了分步安装，因为DNS没有问题，并且可能也可以在Ubuntu 16上运行:NAMESPACE NAME READY STATUS RESTARTS AGEdefault busybox-894550917-7vj3z 1/1 Running 0 15hdefault busybox-894550917-p9vnl 1/1 Running 1 3ddefault gogs-3464422143-cf5wb 1/1 Running 0 16hkube-system dummy-2501624643-pxmgz 1/1 Running 2 3dkube-system etcd-master.cluster.local 1/1 Running 2 3dkube-system kube-apiserver-master.cluster.local 1/1 Running 2 3dkube-system kube-controller-manager-master.cluster.local 1/1 Running 2 3dkube-system kube-discovery-1659614412-vrhv4 1/1 Running 2 3dkube-system kube-dns-4211557627-kpsj4 4/4 Running 8 3dkube-system kube-flannel-ds-d1bgg 2/2 Running 6 3dkube-system kube-flannel-ds-fcp4b 2/2 Running 6 3dkube-system kube-flannel-ds-n7p3m 2/2 Running 6 3dkube-system kube-flannel-ds-tn7nd 2/2 Running 6 3dkube-system kube-flannel-ds-vpk4w 2/2 Running 6 3dkube-system kube-proxy-5nmtn 1/1 Running 2 3dkube-system kube-proxy-gq7bz 1/1 Running 2 3dkube-system kube-proxy-lkkgm 1/1 Running 2 3dkube-system kube-proxy-mlh3v 1/1 Running 1 3dkube-system kube-proxy-sg8n8 1/1 Running 2 3dkube-system kube-scheduler-master.cluster.local 1/1 Running 2 3dkube-system kubernetes-dashboard-3507263287-h9q33 1/1 Running 2 3dI am deploying Kubernetes 1.4 on Ubuntu 16 on Raspberry Pi 3 following the instructions at http://kubernetes.io/docs/getting-started-guides/kubeadm/. The master starts and the minion joins no problem but when I add weave kubedns won't start. Here's the pods:k8s@k8s-master:~$ kubectl get pods --all-namespacesNAMESPACE NAME READY STATUS RESTARTS AGEkube-system etcd-k8s-master 1/1 Running 1 23hkube-system kube-apiserver-k8s-master 1/1 Running 3 23hkube-system kube-controller-manager-k8s-master 1/1 Running 1 23hkube-system kube-discovery-1943570393-ci2m9 1/1 Running 1 23hkube-system kube-dns-4291873140-ia4y8 0/3 ContainerCreating 0 23hkube-system kube-proxy-arm-nfvvy 1/1 Running 0 1hkube-system kube-proxy-arm-tcnta 1/1 Running 1 23hkube-system kube-scheduler-k8s-master 1/1 Running 1 23hkube-system weave-net-4gqd1 0/2 CrashLoopBackOff 54 1hkube-system weave-net-l758i 0/2 CrashLoopBackOff 44 1hThe events log doesn't show anything. getting logs for kube-dns doesn't get anything either.What can I do to debug? 解决方案 UPDATE: As Bryan pointed out, Flannel is not the only overlay network anymore.Note this two hints in the kubeadm install documentation:Flannel is the only network overlay support for arm If you are on another architecture than amd64, you should use the flannel overlay network as described in the multi-platform sectionWhen using Flannel, you need to make a 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.You may also would like to check my automated step-by-step installation for Raspberry Pi 3 with Ansible, since there is no issue with DNS and probably will work with Ubuntu 16 as well:NAMESPACE NAME READY STATUS RESTARTS AGEdefault busybox-894550917-7vj3z 1/1 Running 0 15hdefault busybox-894550917-p9vnl 1/1 Running 1 3ddefault gogs-3464422143-cf5wb 1/1 Running 0 16hkube-system dummy-2501624643-pxmgz 1/1 Running 2 3dkube-system etcd-master.cluster.local 1/1 Running 2 3dkube-system kube-apiserver-master.cluster.local 1/1 Running 2 3dkube-system kube-controller-manager-master.cluster.local 1/1 Running 2 3dkube-system kube-discovery-1659614412-vrhv4 1/1 Running 2 3dkube-system kube-dns-4211557627-kpsj4 4/4 Running 8 3dkube-system kube-flannel-ds-d1bgg 2/2 Running 6 3dkube-system kube-flannel-ds-fcp4b 2/2 Running 6 3dkube-system kube-flannel-ds-n7p3m 2/2 Running 6 3dkube-system kube-flannel-ds-tn7nd 2/2 Running 6 3dkube-system kube-flannel-ds-vpk4w 2/2 Running 6 3dkube-system kube-proxy-5nmtn 1/1 Running 2 3dkube-system kube-proxy-gq7bz 1/1 Running 2 3dkube-system kube-proxy-lkkgm 1/1 Running 2 3dkube-system kube-proxy-mlh3v 1/1 Running 1 3dkube-system kube-proxy-sg8n8 1/1 Running 2 3dkube-system kube-scheduler-master.cluster.local 1/1 Running 2 3dkube-system kubernetes-dashboard-3507263287-h9q33 1/1 Running 2 3d 这篇关于kube-dns和weave-net无法启动的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！ 上岸，阿里云！