kubelet won't start - /etc/kubernetes/pki/ca.crt: no such file or directory

[DK]

Hi,

After installing kubelet it fails to start with: unable to load client CA file /etc/kubernetes/pki/ca.crt: open /etc/kubernetes/pki/ca.crt: no such file or directory

tail -100f /var/log/messages | grep kubelet

Oct 13 10:23:48 master yum[2518]: Installed: kubelet-1.8.1-0.x86_64

Oct 13 10:24:26 master systemd: Starting kubelet: The Kubernetes Node Agent...

Oct 13 10:24:26 master systemd: Started kubelet: The Kubernetes Node Agent.

Oct 13 10:24:26 master kubelet: I1013 10:24:26.518367    2572 feature_gate.go:156] feature gates: map[]

Oct 13 10:24:26 master kubelet: I1013 10:24:26.518581    2572 controller.go:114] kubelet config controller: starting controller

Oct 13 10:24:26 master kubelet: I1013 10:24:26.518587    2572 controller.go:118] kubelet config controller: validating combination of defaults and flags

Oct 13 10:24:26 master kubelet: error: unable to load client CA file /etc/kubernetes/pki/ca.crt: open /etc/kubernetes/pki/ca.crt: no such file or directory

Oct 13 10:24:26 master systemd: kubelet.service: main process exited, code=exited, status=1/FAILURE

Oct 13 10:24:26 master systemd: Unit kubelet.service entered failed state.

cat /etc/centos-release

CentOS Linux release 7.1.1503 (Core)

[Jordan Liggitt]

Installing the kubelet package is the first step of setting up an API server or node.

The next steps are typically to configure the kubelet by running `kubeadm init` to set up an API server or `kubeadm join` to add a node to an existing cluster, then set up a network plugin.

For more information, see:

https://kubernetes.io/docs/setup/independent/install-kubeadm/
https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/9a778de6-3519-4092-b714-1b7d9dc6989c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[DK]

Hi,

When I run kubeadm init I get 

[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:10255/healthz: dial tcp 127.0.0.1:10255: getsockopt: connection refused.

Unfortunately, an error has occurred:

        timed out waiting for the condition

This error is likely caused by that:

        - 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 can't pull the following control plane images:

                - gcr.io/google_containers/kube-apiserver-amd64:v1.8.1

                - gcr.io/google_containers/kube-controller-manager-amd64:v1.8.1

                - gcr.io/google_containers/kube-scheduler-amd64:v1.8.1

You can troubleshoot this for example with the following commands if you're on a systemd-powered system:

        - 'systemctl status kubelet'

        - 'journalctl -xeu kubelet'

couldn't initialize a Kubernetes cluster

[DK]

Hi,

My problem was the version of Docker on the OS. It was using the latest from:

sudo wget -qO- https://get.docker.com/ | sh




I uninstalled and instead ran:

yum install -y docker
systemctl enable docker && systemctl start docker

And then kubeadm init worked kubelet was started successfully