安装带有外部etcd - calico问题的kubernetes

Question

在安装带有外部etcd的k8s多机集群时，我遇到了许多问题。我以前做过两次，在其他网站上，成功，但这次我需要帮助。

calico是根据指南yaml：https://docs.projectcalico.org/manifests/calico.yaml中推荐的内容安装的。

首先，当在config中提到apServer.exargs.ading-Address时，安装calico - calico-node无法到达API就出现了问题。

在那之后，卡布-库贝控制器卡在ContainerCreating状态。我设法通过使用calico-etcd.yaml来修复它，如果是calico.yaml。现在，纸舱已经启动并运行，calicoctl可以在etcd中看到它们。

但核心舱却卡在ConteinerCreating里。这些线我可以在描述豆荚中看到：

  Warning  FailedScheduling        82s (x2 over 88s)  default-scheduler                  
0/1 nodes are available: 1 node(s) had taints that the pod didn't tolerate.
  Normal   Scheduled               80s                default-scheduler                  
Successfully assigned kube-system/coredns-6955765f44-clbhk to master01.<removed>
  Warning  FailedCreatePodSandBox  18s                kubelet, 
master01.<removed>  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "9ab9fe3bd3d4e145c218fe59f6578169fa09075c59718fbe2f
7033d207c4ea4c" network for pod "coredns-6955765f44-clbhk": networkPlugin cni failed to set up pod "coredns-6955765f44-clbhk_kube-system" network: unable to connect to Cilium daemon: failed to create cilium agent client after 30.000000 seconds timeout: Get http:///var/run/cilium/cilium.sock/v1/config: dial unix /var/run/cilium/cilium.sock: connect: no such file or directory
Is the agent running?                                                                                                  
  Normal  SandboxChanged  17s  kubelet, master01.<removed>  Pod sandbox changed, it will be killed and re-created. 

但我不使用纤毛。我用的是棉布。在第一次试纸问题时，我试过纤毛，但是我删除了它，多次使用集群，每次尝试之后也删除了etcd数据。

下面是kubelet配置：

apiVersion: kubeadm.k8s.io/v1beta2
kind: ClusterConfiguration
kubernetesVersion: "v1.17.2"
controlPlaneEndpoint: "192.168.10.100:7443" #balancer ip:port


etcd:
  external:
    endpoints:
    - http://192.168.20.1:2379
    - http://192.168.20.2:2379
    - http://192.168.40.1:2379
    - http://192.168.40.2:2379
    - http://192.168.40.3:2379

#controllerManager:
#  extraArgs:
#    node-monitor-period: "2s"
#    node-monitor-grace-period: "16s"
#    pod-eviction-timeout: "30s"

networking:
  dnsDomain: "cluster.local"
  podSubnet: "10.96.0.0/12"
  serviceSubnet: "172.16.0.0/12"

apiServer:
  timeoutForControlPlane: "60s"
#  extraArgs:
#    advertise-address: "192.168.10.100"
#    bind-address: "192.168.20.1"
#    secure-port: "6443"

kubernetes 1.17.2，etcd 3.3.11，centos 7 x64

感觉问题就在api和etcd之间，但我找不到它。

Answer 1

哦，算了吧。我已经找到了。

在/opt/cni/bin中存在纤毛-cni纤毛-cni.olum-CNI/bin/这些文件明显安装有纤毛，因此它们在kubernetes-cni rpm重新安装中幸存下来。k8s喜欢纤毛，如果它是可用的话。是虫子吗？要我报告吗？