Closed likunding closed 2 years ago
kubectl -n kube-system describe pod xxx
重启containerd后,问题解决,关闭该单
重启containerd后,问题解决,关闭该单
@cyl-007 这个原因有定位吗?
https://github.com/containerd/containerd/blob/f18880a0edecf616a3552e34394b3619ca8e5647/pkg/cri/server/cni_conf_syncer.go#L86 sealos clean的时候不会卸载containerd,但是会删除/etc/cni这个目录,重新部署的的时候会创建这个目录,但是containerd现在忽略了这个event,所以要重启containerd重新加载cni plugin.
重启containerd不起作用
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Restarting containerd doesn't work
【node:k8s-master01】 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message
MemoryPressure False Sat, 03 Aug 2024 14:50:00 +0800 Sat, 03 Aug 2024 11:42:36 +0800 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Sat, 03 Aug 2024 14:50:00 +0800 Sat, 03 Aug 2024 11:42:36 +0800 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Sat, 03 Aug 2024 14:50:00 +0800 Sat, 03 Aug 2024 11:42:36 +0800 KubeletHasSufficientPID kubelet has sufficient PID available Ready False Sat, 03 Aug 2024 14:50:00 +0800 Sat, 03 Aug 2024 11:42:36 +0800 KubeletNotReady container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized
【pod:registry.k8s.io/coredns/coredns:v1.10.1】 Events: Type Reason Age From Message
Warning FailedScheduling 74s (x39 over 3h11m) default-scheduler 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
哪个命令或者组件