k8s的kubelet报错PLEG is not healthy: pleg was last seen active 3m41.603110188s ago

阅读 204

2022-06-28

报错日志

k8s的kubelet报错PLEG is not healthy: pleg was last seen active 3m41.603110188s ago_k8s PLEG

原因一

k8s集群中存在大量状态为Terminating的Pod

解决

rancher kubectl  get pod -n ${NAMESPACE} | grep Terminating | awk '{print $1}' | xargs -i rancher kubectl delete pod {} --force --grace-period=0 -n ${NAMESPACE}

原因二

某个docker进程夯死导致的

for c in `docker ps -aq`; do echo $c; docker inspect $c 1>/dev/null 2>&1; done

如果在某个容器卡住,那么就是该容器导致的

我的是calico容器卡住了
k8s的kubelet报错PLEG is not healthy: pleg was last seen active 3m41.603110188s ago_kubelet PLEG_02
到rancher上面删除,会自动新建

参考文章

​​slave节点notReady,node节点事件显示PLEG is not healthy: pleg was last seen active 3m5.30015447s ago​​


精彩评论(0)

0 0 举报