记一次kubernetes的搭建遇坑coredns状态为CrashLoopBackOff并不断重启

学习kubernetes中，各位大佬知道的可跳过

报错

准备ready0/1 、status: CrashLoopBackOff 伴随着不断重启

 [root@kmaster ~]# kubectl get pod --all-namespaces
    NAMESPACE     NAME                              READY   STATUS             RESTARTS   AGE
    kube-system   coredns-8686dcc4fd-8xh55          0/1     CrashLoopBackOff   7          25m
    kube-system   coredns-8686dcc4fd-98n5p          0/1     CrashLoopBackOff   7          25m

查询日志

[root@kmaster ~]# kubectl logs coredns-8686dcc4fd-8xh55 -n kube-system
.:53
2019-06-02T03:01:48.526Z [INFO] CoreDNS-1.3.1
2019-06-02T03:01:48.526Z [INFO] linux/amd64, go1.11.4, 6b56a9c
CoreDNS-1.3.1
linux/amd64, go1.11.4, 6b56a9c
2019-06-02T03:01:48.526Z [INFO] plugin/reload: Running configuration MD5 = 599b9eb76b8c147408aed6a0bbe0f669
2019-06-02T03:01:54.529Z [ERROR] plugin/errors: 2 6215460374710620394.9107374617267187049. HINFO: read udp 10.32.1.2:42377->223.5.5.5:53: i/o timeout
2019-06-02T03:01:57.529Z [ERROR] plugin/errors: 2 6215460374710620394.9107374617267187049. HINFO: read udp 10.32.1.2:60887->114.114.114.114:53: i/o timeout
2019-06-02T03:01:59.530Z [ERROR] plugin/errors: 2 6215460374710620394.9107374617267187049. HINFO: read udp 10.32.1.2:56568->114.114.114.114:53: i/o timeout
2019-06-02T03:02:00.531Z [ERROR] plugin/errors: 2 6215460374710620394.9107374617267187049. HINFO: read udp 10.32.1.2:53437->114.114.114.114:53: i/o timeout
2019-06-02T03:02:02.531Z [ERROR] plugin/errors: 2 6215460374710620394.9107374617267187049. HINFO: read udp 10.32.1.2:51351->114.114.114.114:53: i/o timeout
2019-06-02T03:02:05.533Z [ERROR] plugin/errors: 2 6215460374710620394.9107374617267187049. HINFO: read udp 10.32.1.2:56134->114.114.114.114:53: i/o timeout
2019-06-02T03:02:08.535Z [ERROR] plugin/errors: 2 6215460374710620394.9107374617267187049. HINFO: read udp 10.32.1.2:36700->114.114.114.114:53: i/o timeout
2019-06-02T03:02:11.537Z [ERROR] plugin/errors: 2 6215460374710620394.9107374617267187049. HINFO: read udp 10.32.1.2:60315->223.5.5.5:53: i/o timeout
E0602 03:02:13.526077       1 reflector.go:134] github.com/coredns/coredns/plugin/kubernetes/controller.go:322: Failed to list *v1.Namespace: Get https://10.96.0.1:443/api/v1/namespaces?limit=500&resourceVersion=0: dial tcp 10.96.0.1:443: i/o timeout
E0602 03:02:13.526077       1 reflector.go:134] github.com/coredns/coredns/plugin/kubernetes/controller.go:322: Failed to list *v1.Namespace: Get https://10.96.0.1:443/api/v1/namespaces?limit=500&resourceVersion=0: dial tcp 10.96.0.1:443: i/o timeout
log: exiting because of error: log: cannot create log: open /tmp/coredns.coredns-8686dcc4fd-8xh55.unknownuser.log.ERROR.20190602-030213.1: no such file or directory

error 报错，开始以为是目录权限问题，经过一番折腾，总算get到重点 ：tcp 10.96.0.1:443: i/o timeout，这很明显是网络不通

经过一番baidu、bing、google及kubernentes、coredns官方文档分析

有位网友提示说在加node之前装 网络插件flannel
经过查看kubectl get pod --all-namespaces -o wide
发现coredns在node1上
重置后重新初始化master，然后安装flannel
之后再将node1和node2加入master
成功！！！
现在coredns在master上了，具体原因有待学习解惑