k8s集群由于某些原因重置,并添加节点后,部分节点状态为NotReady
![](https://img2022.cnblogs.com/blog/2515525/202206/2515525-20220609130057862-59053998.png)
查看系统日志提示
"Unable to update cni config" err="no networks found in /etc/cni/net.d"
"Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized"
![](https://img2022.cnblogs.com/blog/2515525/202206/2515525-20220609125926315-1674161138.png)
解决
查看状态为NotReady节点的/etc/cni/net.d/目录下为空
![](https://img2022.cnblogs.com/blog/2515525/202206/2515525-20220609130421984-1949837763.png)
查看状态为Ready节点的/etc/cni/net.d/目录下存在10-calico.conflist、calico-kubeconfig
![](https://img2022.cnblogs.com/blog/2515525/202206/2515525-20220609130546178-2108141720.png)
复制状态为Ready节点的/etc/cni/net.d/目录下的10-calico.conflist、calico-kubeconfig 到状态为NotReady节点的/etc/cni/net.d/目录下
重启状态为NotReady节点
再次查看节点状态,已正常
![](https://img2022.cnblogs.com/blog/2515525/202206/2515525-20220609131419565-1167212508.png)
原因
可能是手动操作误删除了
记得好像正式环境的k8s正常运行后也出现过这个情况