How to initialize kubenetes to report errors and initialize kubenetes

How to initialize kubenetes to report errors and initialize kubenetes

An error occurred while initializing the kubeletes cluster:

[root@etcd-host1 ~]#[root@etcd-host1 ~]# kubeadm init --kubernetes-version=v1.9.0 --pod-network-cidr=10.244.0.0/16[init] Using Kubernetes version: v1.9.0[init] Using Authorization modes: [Node RBAC][preflight] Running pre-flight checks.        [WARNING FileExisting-crictl]: crictl not found in system path[preflight] Starting the kubelet service[certificates] Generated ca certificate and key.[certificates] Generated apiserver certificate and key.[certificates] apiserver serving cert is signed for DNS names [master kubernetes kubernetes.default kubernetes.default.svc k                 ubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.129.6.211][certificates] Generated apiserver-kubelet-client certificate and key.[certificates] Generated sa key and public key.[certificates] Generated front-proxy-ca certificate and key.[certificates] Generated front-proxy-client certificate and key.[certificates] Valid certificates and keys now exist in "/etc/kubernetes/pki"[kubeconfig] Wrote KubeConfig file to disk: "admin.conf"[kubeconfig] Wrote KubeConfig file to disk: "kubelet.conf"[kubeconfig] Wrote KubeConfig file to disk: "controller-manager.conf"[kubeconfig] Wrote KubeConfig file to disk: "scheduler.conf"[controlplane] Wrote Static Pod manifest for component kube-apiserver to "/etc/kubernetes/manifests/kube-apiserver.yaml"[controlplane] Wrote Static Pod manifest for component kube-controller-manager to "/etc/kubernetes/manifests/kube-controller                 -manager.yaml"[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.[kubelet-check] It seems like the kubelet isn't running or healthy.[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz' failed with error: Get http://localhost:10                 255/healthz: dial tcp [::1]:10255: getsockopt: connection refused.[kubelet-check] It seems like the kubelet isn't running or healthy.[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz' failed with error: Get http://localhost:10                 255/healthz: dial tcp [::1]:10255: getsockopt: connection refused.[kubelet-check] It seems like the kubelet isn't running or healthy.[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz' failed with error: Get http://localhost:10                 255/healthz: dial tcp [::1]:10255: getsockopt: connection refused.[kubelet-check] It seems like the kubelet isn't running or healthy.[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz/syncloop' failed with error: Get http://loc                 alhost:10255/healthz/syncloop: dial tcp [::1]:10255: getsockopt: connection refused.[kubelet-check] It seems like the kubelet isn't running or healthy.[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz/syncloop' failed with error: Get http://loc                 alhost:10255/healthz/syncloop: dial tcp [::1]:10255: getsockopt: connection refused.[kubelet-check] It seems like the kubelet isn't running or healthy.[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz/syncloop' failed with error: Get http://loc                 alhost:10255/healthz/syncloop: dial tcp [::1]:10255: getsockopt: connection refused.[kubelet-check] It seems like the kubelet isn't running or healthy.[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz' failed with error: Get http://localhost:10                 255/healthz: dial tcp [::1]:10255: getsockopt: connection refused.[kubelet-check] It seems like the kubelet isn't running or healthy.[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz/syncloop' failed with error: Get http://loc                 alhost:10255/healthz/syncloop: dial tcp [::1]:10255: getsockopt: connection refused.[kubelet-check] It seems like the kubelet isn't running or healthy.[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz' failed with error: Get http://localhost:10                 255/healthz: dial tcp [::1]:10255: getsockopt: connection refused.Unfortunately, an error has occurred:        timed out waiting for the conditionThis 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)        - There is no internet connection, so the kubelet cannot pull the following control plane images:                - gcr.io/google_containers/kube-apiserver-amd64:v1.9.0                - gcr.io/google_containers/kube-controller-manager-amd64:v1.9.0                - gcr.io/google_containers/kube-scheduler-amd64:v1.9.0If 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@etcd-host1 ~]#

Solution:

Modify the file:

vi /etc/systemd/system/kubelet.service.d/10-kubeadm.conf

Change to the following:

Then execute:

kubeadm reset

Then reinitialize:

kubeadm init --kubernetes-version=v1.9.0 --pod-network-cidr=10.244.0.0/16