Question

我有一个在虚拟盒子中运行的ubuntu 16.04。我使用kubeadm在单个节点上安装了Kubernetes。

但是coredns pod处于Crashloopbackoff状态。

所有其他Pod正在运行。

单个接口（enp0s3）-桥接网络

应用印花布使用 kubectl apply -f https://docs.projectcalico.org/manifests/calico.yaml

output on kubectl describe pod: 
 Type     Reason     Age                  From               Message
  ----     ------     ----                 ----               -------
  Normal   Scheduled  41m                  default-scheduler  Successfully assigned kube-system/coredns-66bff467f8-dxzq7 to kube
  Normal   Pulled     39m (x5 over 41m)    kubelet, kube      Container image "k8s.gcr.io/coredns:1.6.7" already present on machine
  Normal   Created    39m (x5 over 41m)    kubelet, kube      Created container coredns
  Normal   Started    39m (x5 over 41m)    kubelet, kube      Started container coredns
  Warning  BackOff    87s (x194 over 41m)  kubelet, kube      Back-off restarting failed container

Answer 1

我做了一个kubectl logs <coredns-pod>，并在下面找到了错误日志，并查看了提到的link 根据建议，在resolv.conf = /etc/resolv.conf的末尾添加/etc/kubernetes/kubelet/conf.yaml 并重新创建广告连播。

kubectl logs coredns-66bff467f8-dxzq7 -n kube-system 
.:53 [INFO] plugin/reload: Running configuration MD5 = 4e235fcc3696966e76816bcd9034ebc7 CoreDNS-1.6.7 linux/amd64, go1.13.6, da7f65b [FATAL] plugin/loop: Loop (127.0.0.1:34536 -> :53) detected for zone ".", see coredns.io/plugins/loop#troubleshooting. Query: "HINFO 8322382447049308542.5528484581440387393." 
root@kube:/home/kube#

Answer 2

在 /etc/resolv.conf (Host machine) 中注释下面的行并删除 kube-system 命名空间中的 coredns pod。
新的 Pod 进入运行状态 :)

#nameserver 127.0.1.1

带有Calico网络的Coredns处于Crashloopbackoff状态

2 个答案: