kubernetes: failed to load Kubelet config file /var/lib/kubelet/config.yaml after restart

hy folks

after updating my server, I m not able to restart kubernetes.( Master & nodes ) the server was setup with kubeadm

[Feb  6 10:34:25 chgvascldp99 agent: 2019-02-06 10:34:25 CET | ERROR | (domain_forwarder.go:106 in retryTransactions) | Dropped 2 transactions in this retry attempt: 2 for exceeding the retry queue size limit of 30, 0 because the workers are too busy
Feb  6 10:34:25 chgvascldp99 agent: 2019-02-06 10:34:25 CET | ERROR | (config_poller.go:121 in collect) | Unable to collect configurations from provider kubernetes: permanent failure in kubeutil: retry number exceeded
Feb  6 10:34:26 chgvascldp99 systemd: kubelet.service holdoff time over, scheduling restart.
Feb  6 10:34:26 chgvascldp99 systemd: Stopped kubelet: The Kubernetes Node Agent.
Feb  6 10:34:26 chgvascldp99 systemd: Started kubelet: The Kubernetes Node Agent.
Feb  6 10:34:26 chgvascldp99 kubelet: F0206 10:34:26.662744   27634 server.go:189] failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/var/lib/kubelet/config.yaml", error: open /var/lib/kubelet/config.yaml: no such file or directory
Feb  6 10:34:26 chgvascldp99 systemd: kubelet.service: main process exited, code=exited, status=255/n/a
Feb  6 10:34:26 chgvascldp99 systemd: Unit kubelet.service entered failed state.
Feb  6 10:34:26 chgvascldp99 systemd: kubelet.service failed.]

i’ve read on another issue on github someone said to run

kubeadm init per the setup instructions to create the required configuration. the third post on this link but in his cas it was after a new install . I dont know if i’ve to do the same ?

do you know why the config.yaml file disappeared ?

server : 3.10.0-957.5.1.el7.x86_64 kubectl : Major:“1”, Minor:“13”, GitVersion:“v1.13.3” GoVersion:“go1.11.5” Kubernetes : v1.13.3

sig/error_kubelet_config_file

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 17 (8 by maintainers)

Most upvoted comments

I got the same error messages though the file /var/lib/kubelet/config.yaml did exist. After running kubeadm init I found out, that swap was reenabled after a restart.

So doing a swapoff -a fixed it for me.