I have issues with my Linode Cluster: couldn't get current server API group list
When I execute
kubectl get nodes I get this error:
[root@143-42-20-63 ~]# kubectl get nodes
E0131 08:47:53.770167 277316 memcache.go:238] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connect: connection refused
E0131 08:47:53.771171 277316 memcache.go:238] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connect: connection refused
E0131 08:47:53.772634 277316 memcache.go:238] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connect: connection refused
E0131 08:47:53.774060 277316 memcache.go:238] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connect: connection refused
E0131 08:47:53.775444 277316 memcache.go:238] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connect: connection refused
The connection to the server localhost:8080 was refused - did you specify the right host or port?
Any idea of what´s going on? Much appreciated any help in this case.
2 Replies
I had the same issue on Ubuntu 22.04. When I checked the /var/log/syslog I found it out, that somehow the swapiness got reenabled.
What I did is I edited the /etc/fstab file and removed the line, which contains the swap.img line, after this I rebooted the server and everything went back to normal
tlambert
Linode Staff
The first thing I suggest is making sure you're kubeconfig is pointing to the right place. Your error message is indicating localhost which leads me to believe kubectl is either using it's default setup or potentially a self-managed cluster if you also have one of those.
If kubectl was pointing to your LKE kubeconfig, the error would look more like this:
E0320 11:22:54.278137 6572 memcache.go:238] couldn't get current server API group list: Get "https://<long-string-of-numbers-and-letters>.<linode-region-name>.linodelke.net:443/api?timeout=32s": EOF"
If you see an error like the above, it may be related to the health of your cluster. In that case, I suggest opening a ticket to have the Support Team take a closer look.
Regarding the errors on localhost, this post on stack overflow titled missing kubectl config files after install might be helpful. It explains a bit about kubernetes/kubectl versions and how they relate to which ports are supported.