nodelocaldns窗格状态为CrashLoopBackOff

时间:2020-07-31 01:24:28

标签: kubernetes-pod

仅供参考,当谈到docker和kubernetes时,超级傻瓜。

这是我的情况,最后两个 nodelocaldns 窗格处于 CrashLoopBackOff 状态。

root@test-master:~# kubectl get pods -n kube-system  
NAMEREADY   STATUS             RESTARTS   AGE  
calico-kube-controllers-64f98644-9l855   1/1     Running            0          6d21h  
calico-node-8w9tz                        1/1     Running            1          6d21h  
calico-node-cvtrx                        1/1     Running            1          6d21h  
calico-node-glp6x                        1/1     Running            1          6d21h  
coredns-74c9d4d795-4z9xt                 1/1     Running            0          6d2h  
coredns-74c9d4d795-cfc7p                 1/1     Running            1          6d2h  
dns-autoscaler-7d95989447-fngw6          1/1     Running            0          6d21h  
kube-apiserver-test-master               1/1     Running            0          6d21h  
kube-controller-manager-test-master      1/1     Running            1          6d21h  
kube-proxy-b7rjs                         1/1     Running            1          6d2h  
kube-proxy-chc94                         1/1     Running            1          6d2h  
kube-proxy-sx5rt                         1/1     Running            0          6d2h  
kube-scheduler-test-master               1/1     Running            1          6d21h  
kubernetes-dashboard-7c547b4c64-9bsgx    1/1     Running            0          6d21h  
nginx-proxy-test-worker1                 1/1     Running            1          6d21h  
nginx-proxy-test-worker2                 1/1     Running            1          6d21h  
nodelocaldns-5mzlc                       1/1     Running            361        6d21h  
nodelocaldns-5qvhc                       0/1     CrashLoopBackOff   1948       6d21h 
nodelocaldns-lmlpr                       0/1     CrashLoopBackOff   1937       6d21h
root@test-master:~#   

在查看所有三个 nodelocaldns 的日志时,这是我看到的:

root@test-master:~# kubectl logs **nodelocaldns-5mzlc** -n kube-system  
2020/07/25 09:54:38 2020-07-25T09:54:38.452Z [INFO] Tearing down  
2020/07/25 09:54:38 2020-07-25T09:54:38.553Z [INFO] Setting up networking for node cache  
cluster.local.:53 on 169.254.25.10  
in-addr.arpa.:53 on 169.254.25.10  
ip6.arpa.:53 on 169.254.25.10  
.:53 on 169.254.25.10  
2020-07-25T09:54:38.589Z [INFO] CoreDNS-1.2.6  
2020-07-25T09:54:38.589Z [INFO] linux/amd64, go1.11.10,  
CoreDNS-1.2.6  
linux/amd64, go1.11.10,  
 [INFO] plugin/reload: Running configuration MD5 = cd88e46f28ab8d7e0c280ec4dd60bbb9  
root@test-master:~#  

root@test-master:~# kubectl logs **nodelocaldns-5qvhc** -n kube-system  
2020/07/31 00:08:59 2020-07-31T00:08:59.805Z [INFO] Tearing down  
2020/07/31 00:08:59 2020-07-31T00:08:59.889Z [INFO] Setting up networking for node cache  
listen tcp 169.254.25.10:53: bind: address already in use  

root@test-master:~# kubectl logs **nodelocaldns-lmlpr** -n kube-system  
Error from server (InternalError): Internal error occurred: Authorization error (user=kube-apiserver-kubelet-client, verb=get, resource=nodes, subresource=proxy)
root@test-master:~#   

这里有一些初步问题

#1当我为两个工作节点创建ubuntu时,我让它启用了一堆服务,其中一个是DNS。这会导致我当前的问题吗?

#2后两个nodelocaldns pod是否处于 CrashLoopBackOff 状态,因为第一个nodelocaldns pod已在使用169.254.25.10?

0 个答案:

没有答案