Coredns 与 calico 网络处于 Crashloopbackoff 状态

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>

并在下面找到了错误日志并查看了提到的链接 根据建议，在

resolv.conf = /etc/resolv.conf

末尾添加

/etc/kubernetes/kubelet/conf.yaml 

并重新创建 pod。

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（主机）中评论以下行并删除 kube-system 命名空间中的 coredns pod。
新 Pod 处于运行状态:)

• #名称服务器127.0.1.1