kubernetes – 使用网络插件“cni”：cni config unintialized;跳过吊舱

2023年10月8日 458次阅读

我使用
kubeadm kubeadm init创建了
《kubernetes – 使用网络插件“cni”：cni config unintialized;跳过吊舱》kubernetes集群.

我收到/ var / log / messages中的错误消息.

Oct 20 10:09:52 aws08 kubelet: I1020 10:09:52.015921    7116
docker_manager.go:1787] DNS ResolvConfPath exists:
/var/lib/docker/containers/717adf7a8481637ac20a9ba103d8f97635a88bf05f18bd4299f0d164e48f2920/resolv.conf.
Will attempt to add ndots option: options ndots:5 Oct 20 10:09:52
aws08 kubelet: I1020 10:09:52.015963    7116 docker_manager.go:2121]
Calling network plugin cni to setup pod for
kube-dns-2247936740-cjij4_kube-system(3b296413-96aa-11e6-8c40-02fff663a168)
Oct 20 10:09:52 aws08 kubelet: E1020 10:09:52.015982    7116
docker_manager.go:2127] Failed to setup network for pod
"kube-dns-2247936740-cjij4_kube-system(3b296413-96aa-11e6-8c40-02fff663a168)"
using network plugins "cni": cni config unintialized; Skipping pod Oct
20 10:09:52 aws08 kubelet: I1020 10:09:52.018824    7116
docker_manager.go:1492] Killing container
"717adf7a8481637ac20a9ba103d8f97635a88bf05f18bd4299f0d164e48f2920
kube-system/kube-dns-2247936740-cjij4" with 30 second grace period

DNS窗格失败：

kube-system   kube-dns-2247936740-j5rtc        0/3       ContainerCreating   21         1h

如果我禁用了CNI,则DNS pod正在运行.但DNS的问题仍然存在.

禁用cni的方法是在/etc/systemd/system/kubelet.service.d/10-kubeadm.conf中注释KUBELET_NETWORK_ARGS行并重新启动kubelet服务

[Service]
Environment="KUBELET_KUBECONFIG_ARGS=--kubeconfig=/etc/kubernetes/kubelet.conf --require-kubeconfig=true"
Environment="KUBELET_SYSTEM_PODS_ARGS=--pod-manifest-path=/etc/kubernetes/manifests --allow-privileged=true"
# Environment="KUBELET_NETWORK_ARGS=--network-plugin=cni --cni-conf-dir=/etc/cni/net.d --cni-bin-dir=/opt/cni/bin"
Environment="KUBELET_DNS_ARGS=--cluster-dns=100.64.0.10 --cluster-domain=cluster.local"
Environment="KUBELET_EXTRA_ARGS=--v=4"
ExecStart=
ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_SYSTEM_PODS_ARGS $KUBELET_NETWORK_ARGS $KUBELET_DNS_ARGS $KUBELET_EXTRA_ARGS

其次是：

sudo systemctl重启kubelet

最佳答案 我猜你忘记了
setup the pod network.

从文档：

It is necessary to do this before you try to deploy any applications to your cluster, and before kube-dns will start up. Note also that kubeadm only supports CNI based networks and therefore kubenet based networks will not work.

您可以使用以下命令安装pod网络加载项：

kubectl apply -f <add-on.yaml>

例：

kubectl create -f https://git.io/weave-kube

安装Weave Net附加组件.

完成此操作后,您可能需要重新创建kube-dns pod.

点赞