Always getting dial tcp after the successful installation

#1

Hi Experts, can anyone please suggest fix dial tcp connection refused error as every repeated installation facing the same issue? All the time, the cluster is working 5 min, and pods are getting down, facing the same issue again.

command i used for isntallation:
kubeadm init --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=192.168.29.208

Errors:
$ kubectl get pods -A
E1027 16:41:33.397370 6188 memcache.go:265] “Unhandled Error” err=“couldn’t get current server API group list: Get "https://192.168.29.208:6443/api?timeout=32s\”: dial tcp 192.168.29.208:6443: connect: connection refused"
@kubemaster:~$

#2

That would not be a successful install :slight_smile: Just saying!

This sounds like a common error in the install: containerd is incorrectly configured, which makes kube-apiserver “thrash”. To fix this, you’ll need to:

  • reset what kubeadm init does by running kubeadm reset, which will back out the install.
  • fix containerd’s config file, config.toml. Please redo the tasks in the Node Setup page, which are where you most likely made the mistake.
#4

thank you so much Rob, fixed issue after installing containerd package instead container.io package. also applied all other suggested configuration by you. Cluster is working as expected.