search

oomichi / try-kubernetes

12 stars 5 forks source link

failed to deploy k8s v1.12 #55

Closed oomichi closed 5 years ago

oomichi commented 5 years ago

既存の v1.11 までの手順を実行しても、v1.12 では node のステータスが Ready にならない。

$ kubectl get nodes
NAME         STATUS     ROLES    AGE   VERSION
efk-master   NotReady   master   19h   v1.12.0
efk-node01   NotReady   <none>   19h   v1.12.0

以下のように coredns と kube-flannel の Pods が有効にならない。

$ kubectl get pods -n kube-system
NAME                                 READY   STATUS              RESTARTS   AGE
coredns-576cbf47c7-v8v5v             0/1     ContainerCreating   0          19h
coredns-576cbf47c7-zwzdx             0/1     ContainerCreating   0          19h
etcd-efk-master                      1/1     Running             0          19h
kube-apiserver-efk-master            1/1     Running             0          19h
kube-controller-manager-efk-master   1/1     Running             0          19h
kube-flannel-ds-9xkm7                0/1     Pending             0          19h
kube-proxy-s5rbn                     1/1     Running             0          19h
kube-proxy-skmjr                     1/1     Running             0          19h
kube-scheduler-efk-master            1/1     Running             0          19h

coredns の状態

$ kubectl describe pod coredns-576cbf47c7-v8v5v -n kube-system
...
Events:
  Type     Reason           Age                   From                 Message
  ----     ------           ----                  ----                 -------
  Warning  NetworkNotReady  60s (x5367 over 19h)  kubelet, efk-node01  network is not ready: [runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized]

kube-flannel の状態

$ kubectl describe pod kube-flannel-ds-9xkm7 -n kube-system
..
Events:
  Type     Reason            Age                   From               Message
  ----     ------            ----                  ----               -------
  Warning  FailedScheduling  5s (x13861 over 19h)  default-scheduler  0/2 nodes are available: 1 node(s) didn't match node selector, 1 node(s) had taints that the pod didn't tolerate.
oomichi commented 5 years ago

公式ドキュメントの flannel 記述が古かったのが原因。 イノーさんが website/pull/10571 で修正。