ouldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp 127.0.0.1:8080: connect: connection refused

[gpahlevanzadeh]

I installed 3 masters successfully and they're HA. such as:

root@debian:~# kubectl get  nodes
NAME      STATUS   ROLES                       AGE     VERSION
agent1    Ready    <none>                      6h24m   v1.31.4+k3s1
debian    Ready    control-plane,etcd,master   25h     v1.31.4+k3s1
master2   Ready    control-plane,etcd,master   25h     v1.31.4+k3s1
master3   Ready    control-plane,etcd,master   24h     v1.31.4+k3s1

debian is first master, master2 is second master and master3 is third master.
Then I installed an agent with agent1 name.
When I run kubectl get nodes in agent1 machine, I get the following messages:

root@agent1:~# kubectl get nodes 
E1225 03:41:18.927366    7649 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp 127.0.0.1:8080: connect: connection refused"
E1225 03:41:18.933653    7649 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp 127.0.0.1:8080: connect: connection refused"
E1225 03:41:18.938175    7649 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp 127.0.0.1:8080: connect: connection refused"
E1225 03:41:18.945694    7649 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp 127.0.0.1:8080: connect: connection refused"
E1225 03:41:18.958445    7649 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp 127.0.0.1:8080: connect: connection refused"
The connection to the server localhost:8080 was refused - did you specify the right host or port?

My /root/.kube/config is

server: https://192.168.1.106:6443
token: mohsenjoojoo

My agent installation:
curl -sfL https://get.k3s.io | K3S_TOKEN=mohsenjoojoo sh -s - agent --server https://192.168.1.106:6443
My k3s-agent is up:

root@agent1:~# ps ax |grep k3s
   2012 ?        Sl     0:12 /var/lib/rancher/k3s/data/c3b3bbf39f70985bb27180c065eb5928b00f3fad75e5c614e8736017d239b9e0/bin/containerd-shim-runc-v2 -namespace k8s.io -id 1720611259cfb172e4fce0f434a9a37ec0080d1d224dab923b17bc2efad3e2d3 -address /run/k3s/containerd/containerd.sock
   5493 ?        Ssl    2:35 /usr/local/bin/k3s agent

How can I solve my problem?

[brandond]

Only servers have a copy of the admin kubeconfig. To access the apiserver from other nodes, follow the documentation: https://docs.k3s.io/cluster-access#accessing-the-cluster-from-outside-with-kubectl

[gpahlevanzadeh]

I don't have k3s.yaml in agent machine. Do I generate it by command or write it by hand. I have it on my masters.