Score:0

"[kubelet-check]" kubelet not running when: kubeadm init

al flag

When the command: kubeadm init, is commited eventually this error pops up:

[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.

After looking at the journalctl -xeu kubelet, it seems like containerd is not working right. However, containerd is active and running.

Here is the first error in journalctl -xeu kubelet log:

vendor/k8s.io/client-go/informers/factory.go:150: failed to list *v1.Service: Get "https://X.X.X.X:6443/api/v1/services?limit=500&resourceVersion=0": dial tcp X.X.X.X:6443: connect: connection refused vendor/k8s.io/client-go/informers/factory.go:150: Failed to watch *v1.Service: failed to list *v1.Service: Get "https://X.X.X.X:6443/api/v1/services?limit=500&resourceVersion=0": dial tcp X.X.X.X:6443: connect: connection refused
I sit in a Tesla and translated this thread with Ai:

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.