k8s的排错
作者：互联网
解决问题的方案 no runing
systemctl stop kubelet
systemctl stop docker
iptables --flush
iptables -tnat --flush
systemctl start kubelet
systemctl start docker
[root@server2 ~]# kubectl get pod -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-545d6fc579-p6n5f 0/1 Running 0 121m
coredns-545d6fc579-vjnwq 0/1 Running 0 121m
etcd-server2 1/1 Running 0 121m
kube-apiserver-server2 1/1 Running 0 121m
kube-controller-manager-server2 1/1 Running 0 121m
kube-flannel-ds-pmhz2 1/1 Running 0 90m
kube-proxy-hm6mn 1/1 Running 0 121m
kube-scheduler-server2 1/1 Running 0 121m
[root@server2 ~]# systemctl stop kubelet
[root@server2 ~]# systemctl stop docker
[root@server2 ~]# iptables --flush
[root@server2 ~]# iptables -tnat --flush
[root@server2 ~]# systemctl start kubelet
[root@server2 ~]# systemctl start docker
[root@server2 ~]# kubectl get pod -n kube-system
The connection to the server 172.25.40.2:6443 was refused - did you specify the right host or port?
[root@server2 ~]# kubectl get pod -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-545d6fc579-p6n5f 0/1 Running 0 124m
coredns-545d6fc579-vjnwq 0/1 Completed 0 124m
etcd-server2 0/1 Running 1 124m
kube-apiserver-server2 0/1 Running 1 124m
kube-controller-manager-server2 0/1 Running 1 124m
kube-flannel-ds-pmhz2 0/1 Completed 0 94m
kube-proxy-hm6mn 0/1 Error 0 124m
kube-scheduler-server2 0/1 Running 1 124m
[root@server2 ~]# kubectl get pod -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-545d6fc579-p6n5f 1/1 Running 1 124m
coredns-545d6fc579-vjnwq 0/1 Running 1 124m
etcd-server2 1/1 Running 1 125m
kube-apiserver-server2 0/1 Running 1 125m
kube-controller-manager-server2 0/1 Running 1 125m
kube-flannel-ds-pmhz2 1/1 Running 1 94m
kube-proxy-hm6mn 1/1 Running 1 124m
kube-scheduler-server2 1/1 Running 1 125m
[root@server2 ~]# kubectl get pod -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-545d6fc579-p6n5f 1/1 Running 1 124m
coredns-545d6fc579-vjnwq 1/1 Running 1 124m
etcd-server2 1/1 Running 1 125m
kube-apiserver-server2 0/1 Running 1 125m
kube-controller-manager-server2 0/1 Running 1 125m
kube-flannel-ds-pmhz2 1/1 Running 1 94m
kube-proxy-hm6mn 1/1 Running 1 124m
kube-scheduler-server2 1/1 Running 1 125m
[root@server2 ~]# kubectl get pod -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-545d6fc579-p6n5f 1/1 Running 1 124m
coredns-545d6fc579-vjnwq 1/1 Running 1 124m
etcd-server2 1/1 Running 1 125m
kube-apiserver-server2 1/1 Running 1 125m
kube-controller-manager-server2 0/1 Running 1 125m
kube-flannel-ds-pmhz2 1/1 Running 1 94m
kube-proxy-hm6mn 1/1 Running 1 124m
kube-scheduler-server2 1/1 Running 1 125m
[root@server2 ~]# kubectl get pod -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-545d6fc579-p6n5f 1/1 Running 1 124m
coredns-545d6fc579-vjnwq 1/1 Running 1 124m
etcd-server2 1/1 Running 1 125m
kube-apiserver-server2 1/1 Running 1 125m
kube-controller-manager-server2 0/1 Running 1 125m
kube-flannel-ds-pmhz2 1/1 Running 1 94m
kube-proxy-hm6mn 1/1 Running 1 124m
kube-scheduler-server2 1/1 Running 1 125m
[root@server2 ~]# kubectl get pod -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-545d6fc579-p6n5f 1/1 Running 1 124m
coredns-545d6fc579-vjnwq 1/1 Running 1 124m
etcd-server2 1/1 Running 1 125m
kube-apiserver-server2 1/1 Running 1 125m
kube-controller-manager-server2 1/1 Running 1 125m
kube-flannel-ds-pmhz2 1/1 Running 1 94m
kube-proxy-hm6mn 1/1 Running 1 124m
kube-scheduler-server2 1/1 Running 1 125m
标签：kube,545d6fc579,125m,124m,排错,server2,Running,k8s 来源： https://blog.csdn.net/Antonhu/article/details/117597848