Score:0

/etc/kubernetes/kubelet.conf: no such file or directory

cn flag

I try to upgrade a node in a demo-cluster:

root@cluster3-worker2:~# sudo kubeadm upgrade node

couldn't create a Kubernetes client from file "/etc/kubernetes/kubelet.conf": failed to load admin kubeconfig: open /etc/kubernetes/kubelet.conf: no such file or directory
To see the stack trace of this error execute with --v=5 or higher

Option --v=5 did not reveal new information.

Any clue what could be help here?

I am following this guide: Upgrade Worker Node

in flag
It's almost certainly because it is using some built-in [kubeadm config](https://pkg.go.dev/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta2#ClusterConfiguration) versus using _the_ kubeadm config that points to your actual on-disk kubelet config. Having said that, _usually_ the Node upgrade path is (1) upgrade the `kubelet` binary (2) `systemctl restart kubelet.service` (3) profit
Score:1
cn flag

This was my mistake.

The node was never in the cluster before. So this was not an upgrade, but an initial join.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.