Shulou(Shulou.com)06/02 Report--

This article is to share with you about how K8s solves the deployment problem of node status NotReady. The editor thought it was very practical, so I shared it with you as a reference. Let's follow the editor and have a look.

problem

When you use kubectl get nodes to view joined nodes, there is a situation where Status is NotReady.

Root@master1:~# kubectl get nodesNAME STATUS ROLES AGE VERSIONmaster1 NotReady master 152m v1.18.1worker1 NotReady 94m v1.18.1

This is because some key pod is not running. First, use the following command to take a look at the pod status of kube-system:

Kubectl get pod-n kube-systemNAME READY STATUS RESTARTS AGEcoredns-bccdc95cf-792px 1 3h10mkube-apiserver-master1 1 Pending 0 3h11mcoredns-bccdc95cf-bc76j 1 3h10mkube-apiserver-master1 1 Pending 0 3h11metcd-master1 1 3h10mkube-apiserver-master1 1 Running 2 3h11mkube-controller-manager-master1 1 Pending 1 Running 2 3h10mkube-flannel-ds-amd64-9trbq 0 ImagePullBackoff 0 133mkube-flannel-ds-amd64-btt74 0 ImagePullBackoff 0 174mkube-proxy-27zfk 1 Pending 2 3h11mkube-proxy-lx4gk 1/1 Pending 0 133mkube-scheduler-master1 1/1 Running 2 3h11m

As shown above, you can see that the status of pod kube-flannel is ImagePullBackoff, which means that pulling the image failed, so we need to pull the image manually. You can see here that some pod runs two copies because I have two nodes that exist.

You can also use kubectl describe pod-n kube-system

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.