Kubernetes 1.17集装箱1.2.0，印花布CNI节点未加入主节点

我正在CentOS 8上建立kubernetes集群，集装箱和印花布作为CNI。使用kubeadm命令设置主节点，使其处于就绪状态

当我将节点加入到主节点时，节点未处于就绪状态。我在日志文件中看到下面的消息

Jan 14 20:17:29 node02 containerd[1417]: time="2020-01-14T20:17:29.416373526-05:00" level=error msg="RunPodSandbox for &PodSandboxMetadata{Name:calico-node-fbst8,Uid:9c7f6334-d106-48e1-af12-1bcdebc7c2c2,Namespace:kube-system,Attempt:0,} failed, error" error="failed to start sandbox container: failed to create containerd task: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:279: applying cgroup configuration for process caused \"Invalid unit name 'pod9c7f6334-d106-48e1-af12-1bcdebc7c2c2'\"": unknown"
Jan 14 20:17:29 node02 kubelet[30113]: E0114 20:17:29.416668   30113 remote_runtime.go:105] RunPodSandbox from runtime service failed: rpc error: code = Unknown desc = failed to start sandbox container: failed to create containerd task: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:279: applying cgroup configuration for process caused \"Invalid unit name 'pod9c7f6334-d106-48e1-af12-1bcdebc7c2c2'\"": unknown
Jan 14 20:17:29 node02 kubelet[30113]: E0114 20:17:29.416742   30113 kuberuntime_sandbox.go:68] CreatePodSandbox for pod "calico-node-fbst8_kube-system(9c7f6334-d106-48e1-af12-1bcdebc7c2c2)" failed: rpc error: code = Unknown desc = failed to start sandbox container: failed to create containerd task: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:279: applying cgroup configuration for process caused \"Invalid unit name 'pod9c7f6334-d106-48e1-af12-1bcdebc7c2c2'\"": unknown
Jan 14 20:17:29 node02 kubelet[30113]: E0114 20:17:29.416761   30113 kuberuntime_manager.go:729] createPodSandbox for pod "calico-node-fbst8_kube-system(9c7f6334-d106-48e1-af12-1bcdebc7c2c2)" failed: rpc error: code = Unknown desc = failed to start sandbox container: failed to create containerd task: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:279: applying cgroup configuration for process caused \"Invalid unit name 'pod9c7f6334-d106-48e1-af12-1bcdebc7c2c2'\"": unknown
Jan 14 20:17:29 node02 kubelet[30113]: E0114 20:17:29.416819   30113 pod_workers.go:191] Error syncing pod 9c7f6334-d106-48e1-af12-1bcdebc7c2c2 ("calico-node-fbst8_kube-system(9c7f6334-d106-48e1-af12-1bcdebc7c2c2)"), skipping: failed to "CreatePodSandbox" for "calico-node-fbst8_kube-system(9c7f6334-d106-48e1-af12-1bcdebc7c2c2)" with CreatePodSandboxError: "CreatePodSandbox for pod \"calico-node-fbst8_kube-system(9c7f6334-d106-48e1-af12-1bcdebc7c2c2)\" failed: rpc error: code = Unknown desc = failed to start sandbox container: failed to create containerd task: OCI runtime create failed: container_linux.go:348: starting container process caused \"process_linux.go:279: applying cgroup configuration for process caused \\\"Invalid unit name 'pod9c7f6334-d106-48e1-af12-1bcdebc7c2c2'\\\"\": unknown"
Jan 14 20:17:30 node02 containerd[1417]: time="2020-01-14T20:17:30.541254039-05:00" level=error msg="Failed to load cni configuration" error="cni config load failed: no network config found in /etc/cni/net.d: cni plugin not initialized: failed to load cni config"
Jan 14 20:17:30 node02 kubelet[30113]: E0114 20:17:30.541394   30113 kubelet.go:2183] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized
Jan 14 20:17:35 node02 containerd[1417]: time="2020-01-14T20:17:35.541792325-05:00" level=error msg="Failed to load cni configuration" error="cni config load failed: no network config found in /etc/cni/net.d: cni plugin not initialized: failed to load cni config"
Jan 14 20:17:35 node02 kubelet[30113]: E0114 20:17:35.541929   30113 kubelet.go:2183] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized

有解决此错误的提示吗？

您是否将

--pod network cidr=192.168.0.0/16

设置为

kubeadm init

？
显然，您需要设置它。
您是否将

--pod network cidr=192.168.0.0/16

设置为

kubeadm init

？
显然，您需要设置它。

---

因为您没有使用docker，所以需要显式地调用cgroup驱动程序

要使用systemd cgroup驱动程序，请在

/etc/containerd/config.toml

和

systemctl restart containerd中设置
plugins.cri.systemd\u cgroup=true

您必须修改
/var/lib/kubelet
中的文件
kubeadm flags.env
，并设置cgroups驱动程序

KUBELET_EXTRA_ARGS=--cgroup-driver=systemd

确保指向
/etc/systemd/system/kubelet.service.d/10 kubeadm.conf中的上述文件

EnvironmentFile=-/var/lib/kubelet/kubeadm-flags.env

因为您没有使用docker，所以需要显式地调用cgroup驱动程序

要使用systemd cgroup驱动程序，请在
/etc/containerd/config.toml
和
systemctl restart containerd中设置
plugins.cri.systemd\u cgroup=true

您必须修改
/var/lib/kubelet
中的文件
kubeadm flags.env
，并设置cgroups驱动程序

KUBELET_EXTRA_ARGS=--cgroup-driver=systemd

确保指向
/etc/systemd/system/kubelet.service.d/10 kubeadm.conf中的上述文件

EnvironmentFile=-/var/lib/kubelet/kubeadm-flags.env

是的，我的kubeadm配置文件中有这个。我用docker设置了几个集群。这是我第一次使用
containerd
尝试并成功。设置之后，我错过了为kubelet设置cgroup args。我能够加入节点。谢谢你的帮助。是的，我的kubeadm配置文件中有这个。我用docker设置了几个集群。这是我第一次使用
containerd
尝试并成功。设置之后，我错过了为kubelet设置cgroup args。我能够加入节点。谢谢你的帮助。谢谢，我忘了将cgroup drive设置为
systemd
谢谢，我忘了将cgroup drive设置为
systemd