一回のkubernetesの建造は穴corednsの状態にぶつかってCrashLoopBackOffになってそして絶えず再起動することを覚えます
3374 ワード
kubernetes公式サイトのドキュメントに従ってインストールすると、corednsは常にCrashLoopBackOff状態であることがわかります。
誤報
準備ready 0/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がnode 1の上でリセットした后にmasterを再初期化することを発见して、それからflannelをインストールした后にnode 1とnode 2をmasterに参加して成功します!!!今corednsはmasterの上で、具体的な原因は学習して困惑を解く必要があります
[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