In the k8s environment, after the server is restarted, all nodes are in noready state and the pod state is running, but none of the docker containers are up.

After restarting the k8s environment, you may encounter various problems. Today, we will record the problems in this situation:

In the k8s environment, after the server is restarted, all nodes are in noready state and the pod state is running, but none of the docker containers are up.

All nodes are in NotReady state
insert image description here
All pods are in Running state
insert image description here
All containers have no state
insert image description here

Solution:

In this case, the hostname should not be changed. Remember to restart the server after changing the hostname.

vi /etc/hostname
192.168.37.41 请设置为:master 
192.168.37.42 请设置为:node1 
192.168.37.43 请设置为:node2

As shown below:
insert image description here

Guess you like

Origin blog.csdn.net/simpleness_/article/details/131150368