kubectl: 'The connection to the server localhost:8080 was refused - did you specify the right host or port?'

Cause: kubectl couldn't find a usable kubeconfig, so it fell back to its old built-in default of http://localhost:8080. The API server is almost never there. It means kubectl has no cluster configured for the user or shell running it, not that the cluster is down. Common situations: - Right after kubeadm init: the admin kubeconfig exists only in /etc/kubernetes/admin.conf and hasn't been copied for your user. - Running kubectl with sudo, as a different user, in CI or in a container, where ~/.kube/config isn't present. - KUBECONFIG points to a file that doesn't exist or a wrong path, or the current context is empty. - Docker Desktop, minikube, kind or k3s isn't started, or its context isn't selected (k3s writes its config to /etc/rancher/k3s/k3s.yaml). How to check: echo $KUBECONFIG; ls -l ~/.kube/config; kubectl config current-context; kubectl config view --minify (shows the server URL kubectl will use). Fix: 1. kubeadm control-plane node: mkdir -p $HOME/.kube; sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config; sudo chown $(id -u):$(id -g) $HOME/.kube/config. 2. Local tools: start the cluster (minikube start, kind create cluster, enable Kubernetes in Docker Desktop) and pick its context with kubectl config use-context <name>. 3. Managed clusters: regenerate the kubeconfig (aws eks update-kubeconfig, gcloud container clusters get-credentials, az aks get-credentials). 4. Point at a specific file when needed: export KUBECONFIG=/path/to/config or kubectl --kubeconfig /path/to/config ... After: kubectl cluster-info should show the real API server address, and kubectl get nodes should work. Keep admin kubeconfigs readable only by your user (chmod 600). Sources: https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/ https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/ https://discuss.kubernetes.io/t/the-connection-to-the-server-localhost-8080-was-refused-did-you-specify-the-right-host-or-port/1464