I am trying to build new cluster using kubeadm and Hardway as well. Most of the times I experience below error after installing all cluster components. command: kubectl cluster-info result: the connection to the server :6443 was refused - did you specify the right host or port? Is there any order…

You might want to run kubeadm with -v to get verbose output from the logs. A first guess without more information is that the firewall is blocking it.

Here’s a link the same issue . The commnads below fixed the issue. sudo -i swapoff -a exit strace -eopenat kubectl version and you can type kubectl get nodes again.

Hey folks, First of all your kubeadm init finished well? Did you copy the admin configuration for your $HOME/.kube/config?

[image] Bitenca: kubeadm init yes I have done that, and kubectl config view show right config file.

Hey Raj, Nice! Did you try connect in localhost port 6443? Is there 6443 port for kube-apiserver open? Which test did you make? I’d like to help you to solve that. :slight_smile:

Broken cluster

General Discussions

hvauto January 23, 2025, 9:52am 7

kubectl cluster-info | grep -oP ‘(?<=server: ).*(?=:6443)’

Topic		Replies	Views
Connection to the server localhost:8080 was refused General Discussions	3	8817	October 12, 2020
Crashing cluster after kubeadm on VPS General Discussions development , network	0	439	June 10, 2023
Dial tcp X.X.X.X:6443: connect: connection refused General Discussions development	0	1711	March 1, 2024
I keep having issues with my cluster General Discussions	0	752	May 30, 2024
[ERROR] kubeadm init error: connection refused General Discussions	8	8385	April 4, 2023

Broken cluster

Related topics