Kubernetes 服务器重新启动后群集工作节点未就绪
当我重新启动主节点和工作节点时,工作节点将从就绪变为未就绪Kubernetes 服务器重新启动后群集工作节点未就绪,kubernetes,Kubernetes,当我重新启动主节点和工作节点时,工作节点将从就绪变为未就绪 kubectl get节点的结果 NAME STATUS ROLES AGE VERSION XXX NotReady work 13d v1.17.2 XXX Ready master 13d v1.17.2 NAMESPACE NAME
kubectl get节点的结果
NAME STATUS ROLES AGE VERSION
XXX NotReady work 13d v1.17.2
XXX Ready master 13d v1.17.2
NAMESPACE NAME READY STATUS RESTARTS AGE
default postgres 1/1 Running 0 20m
default user-api 3/3 Running 0 20m
ingress-nginx nginx-ingress-controller 1/1 Running 3 10d
kube-system coredns 1/1 Running 4 13d
kube-system coredns 1/1 Running 4 13d
kube-system etcd 1/1 Running 4 13d
kube-system kube-apiserver 1/1 Running 4 13d
kube-system kube-controller-manager 1/1 Running 4 13d
kube-system kube-flannel-ds-amd64 1/1 Running 3 13d
kube-system kube-flannel-ds-amd64 1/1 Running 5 13d
kube-system kube-proxy 1/1 Running 4 13d
kube-system kube-proxy 1/1 Running 3 13d
kube-system kube-scheduler 1/1 Running 4 13d
kubectl get pod的结果——所有名称空间
NAME STATUS ROLES AGE VERSION
XXX NotReady work 13d v1.17.2
XXX Ready master 13d v1.17.2
NAMESPACE NAME READY STATUS RESTARTS AGE
default postgres 1/1 Running 0 20m
default user-api 3/3 Running 0 20m
ingress-nginx nginx-ingress-controller 1/1 Running 3 10d
kube-system coredns 1/1 Running 4 13d
kube-system coredns 1/1 Running 4 13d
kube-system etcd 1/1 Running 4 13d
kube-system kube-apiserver 1/1 Running 4 13d
kube-system kube-controller-manager 1/1 Running 4 13d
kube-system kube-flannel-ds-amd64 1/1 Running 3 13d
kube-system kube-flannel-ds-amd64 1/1 Running 5 13d
kube-system kube-proxy 1/1 Running 4 13d
kube-system kube-proxy 1/1 Running 3 13d
kube-system kube-scheduler 1/1 Running 4 13d
如何检查此问题?尝试重新启动节点的
kubelet
,该节点处于notReady
状态,它可能会解决您的问题
下面的命令可以提供帮助:
systemctl restart kubelet
节点未就绪时的kubectl节点日志是命令
kubectl logs node
?对不起,我的意思是kubelet logs有太多消息,我找不到任何有用的错误输出。你能得到kubectl的输出来描述节点名吗?你能在kubelet日志中注册吗?此外,还要对kubelet日志中的任何错误进行grep。