[root@k8-master ~]# kubeadm init [controlplane] Wrote Static Pod manifest for component kube-scheduler to "/etc/kubernetes/manifests/kube-scheduler.yaml" [etcd] Wrote Static Pod manifest for a local etcd instance to "/etc/kubernetes/manifests/etcd.yaml" [init] Waiting for the kubelet to boot up the control plane as Static Pods from directory "/etc/kubernetes/manifests". [init] This might take a minute or longer if the control plane images have to be pulled. Unfortunately, an error has occurred: timed out waiting for the condition This error is likely caused by: - The kubelet is not running - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled) - Either there is no internet connection, or imagePullPolicy is set to "Never", so the kubelet cannot pull or find the following control plane images: - k8s.gcr.io/kube-apiserver-amd64:v1.10.2 - k8s.gcr.io/kube-controller-manager-amd64:v1.10.2 - k8s.gcr.io/kube-scheduler-amd64:v1.10.2 - k8s.gcr.io/etcd-amd64:3.1.12 (only if no external etcd endpoints are configured)
If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands: - 'systemctl status kubelet' - 'journalctl -xeu kubelet' couldn't initialize a Kubernetes cluster [root@k8-master ~]# systemctl status kubelet â kubelet.service - kubelet: The Kubernetes Node Agent Loaded: loaded (/etc/systemd/system/kubelet.service; enabled; vendor preset: disabled) Drop-In: /etc/systemd/system/kubelet.service.d ââ10-kubeadm.conf Active: active (running) since Mon 2018-05-07 21:45:11 AEST; 18h ago Docs: http://kubernetes.io/docs/ Main PID: 13861 (kubelet) CGroup: /system.slice/kubelet.service ââ13861 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --pod-manifest... May 08 15:52:51 k8-master.my.domian.com kubelet[13861]: W0508 15:52:51.055636 13861 cni.go:171] Unable to update cni config: No ne.../net.d May 08 15:52:51 k8-master.my.domian.com kubelet[13861]: E0508 15:52:51.055940 13861 kubelet.go:2125] Container runtime network not...alized May 08 15:52:52 k8-master.my.domian.com kubelet[13861]: E0508 15:52:52.184125 13861 summary.go:102] Failed to get system container stats... [root@k8-master ~]# journalctl -xeu kubelet May 08 15:50:14 k8-master.my.domian.com kubelet[13861]: W0508 15:50:14.526580 13861 container_manager_linux.go:794] MemoryAccounting not en May 08 15:50:15 k8-master.my.domian.com kubelet[13861]: W0508 15:50:15.928944 13861 cni.go:171] Unable to update cni config: No networks fo May 08 15:50:15 k8-master.my.domian.com kubelet[13861]: E0508 15:50:15.929071 13861 kubelet.go:2125] Container runtime network not ready: N May 08 15:50:20 k8-master.my.domian.com kubelet[13861]: W0508 15:50:20.932914 13861 cni.go:171] Unable to update cni config: No networks fo May 08 15:50:20 k8-master.my.domian.com kubelet[13861]: E0508 15:50:20.933153 13861 kubelet.go:2125] Container runtime network not ready: N May 08 15:50:21 k8-master.my.domian.com kubelet[13861]: E0508 15:50:21.829601 13861 summary.go:102] Failed to get system container stats fo May 08 15:50:25 k8-master.my.domian.com kubelet[13861]: W0508 15:50:25.937301 13861 cni.go:171] Unable to update cni config: No networks fo May 08 15:50:25 k8-master.my.domian.com kubelet[13861]: E0508 15:50:25.937555 13861 kubelet.go:2125] Container runtime network not ready: N May 08 15:50:30 k8-master.my.domian.com kubelet[13861]: W0508 15:50:30.939636 13861 cni.go:171] Unable to update cni config: No networks fo -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.