2016-12-28 435 views
3

我使用kubeadm init来初始化Kubernetes,并且我使用kubeadm reset重置它时,我发现--pod-network-cidr是错误的。修正之后我试图用kubeadm给init Kubernetes又像Kubernetes在执行kubeadm重置后未能为pod设置网络

kubeadm init --use-kubernetes-version v1.5.1 --external-etcd endpoints=http://10.111.125.131:2379 --pod-network-cidr=10.244.0.0/16 

然后我得到的节点上一些错误

12月 28 15:30:55 ydtf-node-137 kubelet[13333]: E1228 15:30:55.838700 13333 cni.go:255] Error adding network: no IP addresses available in network: cbr0 
12月 28 15:30:55 ydtf-node-137 kubelet[13333]: E1228 15:30:55.838727 13333 cni.go:209] Error while adding to cni network: no IP addresses available in network: cbr0 
12月 28 15:30:55 ydtf-node-137 kubelet[13333]: E1228 15:30:55.838781 13333 docker_manager.go:2201] Failed to setup network for pod "test-701078429-tl3j2_default(6945191b-ccce-11e6-b53d-78acc0f9504e)" using network plugins "cni": no IP addresses available in network: cbr0; Skipping pod 
12月 28 15:30:56 ydtf-node-137 kubelet[13333]: E1228 15:30:56.205596 13333 pod_workers.go:184] Error syncing pod 6945191b-ccce-11e6-b53d-78acc0f9504e, skipping: failed to "SetupNetwork" for "test-701078429-tl3j2_default" with SetupNetworkError: "Failed to setup network for pod \"test-701078429-tl3j2_default(6945191b-ccce-11e6-b53d-78acc0f9504e)\" using network plugins \"cni\": no IP addresses available in network: cbr0; Skipping pod" 

Dec 29 10:20:02 ydtf-node-137 kubelet: E1229 10:20:02.065142 22259 pod_workers.go:184] Error syncing pod 235cd9c6-cd6c-11e6-a9cd-78acc0f9504e, skipping: failed to "SetupNetwork" for "test-701078429-zmkdf_def ault" with SetupNetworkError: "Failed to setup network for pod \"test-701078429-zmkdf_default(235cd9c6-cd6c-11e6-a9cd-78acc0f9504e)\" using network plugins \"cni\": \"cni0\" already has an IP address different from 10.244.1.1/24; Skipping pod"

为什么我不能为新豆荚创建一个网络?

顺便说一下,我使用绒布作为网络提供商,它工作正常。

[[email protected] k8s151]# kubectl get pods --all-namespaces -o wide 
NAMESPACE  NAME          READY  STATUS      RESTARTS AGE  IP    NODE 
default  test-701078429-tl3j2      0/1  ContainerCreating 0   2h  <none>   ydtf-node-137 
kube-system dummy-2088944543-hd7b7     1/1  Running    0   2h  10.111.125.131 ydtf-master-131 
kube-system kube-apiserver-ydtf-master-131   1/1  Running    7   2h  10.111.125.131 ydtf-master-131 
kube-system kube-controller-manager-ydtf-master-131 1/1  Running    0   2h  10.111.125.131 ydtf-master-131 
kube-system kube-discovery-1769846148-bjgp8   1/1  Running    0   2h  10.111.125.131 ydtf-master-131 
kube-system kube-dns-2924299975-q8x2m     4/4  Running    0   2h  10.244.0.3  ydtf-master-131 
kube-system kube-flannel-ds-3fsjh      2/2  Running    0   2h  10.111.125.137 ydtf-node-137 
kube-system kube-flannel-ds-89r72      2/2  Running    0   2h  10.111.125.131 ydtf-master-131 
kube-system kube-proxy-7w8c4       1/1  Running    0   2h  10.111.125.137 ydtf-node-137 
kube-system kube-proxy-jk6z6       1/1  Running    0   2h  10.111.125.131 ydtf-master-131 
kube-system kube-scheduler-ydtf-master-131   1/1  Running    0   2h  10.111.125.131 ydtf-master-131 

回答

5

我搞清楚,如果你改变--pod网络,CIDR当你通过kubeadm初始化重新初始化kubernetes,你应该删除一些自动创建的东西,只要按照下面你之前的步骤再次执行kubeadm初始化

  1. 执行Kubeadm在主节点和复位

  2. 执行etcdctl rm - 递归注册表在etcd中重置数据。

  3. 室射频的/ var/lib中/ CNI上主和节点
  4. 室射频/运行/绒布上主和节点
  5. 室射频的/ etc/CNI上主站和节点
  6. 的ifconfig cni0向下上主和节点
  7. brctl delbr cni0上主和节点

现在,我kubernets工作正常:)

0

我也有类似的问题,在这种情况下,修复是对法兰绒荚网络应用到集群:

wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml 
kubectl apply -f kube-flannel.yml 
0

后我有一个问题更改--pod-network-cidrjoin报告成功,但没有添加节点。 kubeadm reset和重新加入没有效果。重置后通过apt-get remove kubelet kubeadm kubectl kubernetes-cni解决,然后码头和/或机器重新启动,然后重新安装,然后再重新安装。