[root @ master images] # kubectl get nodes
NAME the STATUS AGE
Master.ian.com Ready 2 h
Node1.ian.com Ready 2 h
Node2.ian.com Ready 2 h
[root @ master images] # kubectl get the pods - all - namespaces
The NAMESPACE NAME READY STATUS RESTARTS AGE
Kube - system Running etcd-master.ian.com 1/1 0 2 h
Kube - system Running kube-apiserver-master.ian.com 1/1 0 2 h
Kube - system Running kube-controller-manager-master.ian.com 1/1 0 2 h
Kube - system kube - discovery - 982812725-1/1 txq7n Running 0 2 h
Kube - system kube - DNS - 2247936740 - c5fy2 0/3 ContainerCreating 0 2 h
Kube - system kube - proxy - amd64-50 t6o Running 1/1 0 2 h
Kube - system kube - proxy - amd64-1/1 kruyg Running 0 2 h
Kube - system kube - proxy - amd64-1/1 o7dk5 Running 0 2 h
Kube - system Running kube-scheduler-master.ian.com 1/1 0 2 h
[root @ master images] # kubectl describe -n kube - system pod kube - DNS - 2247936740 - c5fy2
Events:
FirstSeen LastSeen Count From SubobjectPath Type a tiny Message
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
2 h 0 s 7639} {kubelet master.ian.com Warning FailedSync Error syncing pod, skipping: failed to "SetupNetwork" for "kube - DNS - 2247936740 - c5fy2_kube - system" with SetupNetworkError: "failed to setup network for pod " kube - DNS - 2247936740 - c5fy2_kube - system (9 aecaa07 - c291f315c e6 - a988 a132-11-000), "using the network the plugins " the cni \ ": the cni config unintialized; Skipping pod
"
CodePudding user response:
~ ~ I also appeared the same problemCodePudding user response:
Reason seems to be "/etc/the cni/.net. D." under no cni configuration files, I don't know yet if set configuration fileCodePudding user response:
After you install weave or flannel network, kube - DNS must configure the network to Running