Kubernetes新手求助：执行kubectl version命令时遇连接拒绝错误

Hey there! As a Kubernetes newbie, it's totally normal to hit this connection snag when you're just getting started. Let's work through the most common fixes step by step:

1. First, Check if Your Kubernetes Cluster is Running #

This is the #1 reason for this error—your cluster's API server (which listens on port 6443) isn't up and running yet. Here's how to check and fix it based on your setup:

• If you're using Minikube:
  Run minikube status to check the cluster state. If it shows anything other than Running, start it with:

  minikube start
  

  Minikube will automatically configure your kubectl context once it's up and running.
• If you're using Docker Desktop's Kubernetes:
  Open Docker Desktop, head to the Settings > Kubernetes tab, and make sure "Enable Kubernetes" is checked and the status shows "Running". If not, enable it and wait a minute for the cluster to initialize.
• If you deployed with kubeadm (Linux):
  Check the kube-apiserver service status with:

  sudo systemctl status kube-apiserver
  

  If it's not running, start it with:

  sudo systemctl start kube-apiserver
  

  For Windows self-hosted clusters, look for "Kubernetes API Server" in the Windows Services list and ensure it's started.

2. Verify Your kubectl Configuration (kubeconfig) #

kubectl relies on a config file to know how to connect to your cluster. If this file is missing or misconfigured, it'll default to trying 127.0.0.1:6443 even if your cluster is elsewhere.

• Check your current config with:

  kubectl config view
  

  Look for the server field under your active context—make sure it points to your cluster's actual API server address.
• If the config is wrong, switch to the correct context (if you have one):

  kubectl config use-context <your-cluster-context-name>
  

  For Minikube/Docker Desktop, starting the cluster usually auto-updates this config for you. If you need to refresh it manually, Minikube provides:

  minikube update-context
  

3. Check if Port 6443 is Being Listened On #

If the cluster should be running but you still get the error, confirm something is actually listening on port 6443:

• Windows:
  Open Command Prompt and run:

  netstat -ano | findstr :6443
  

  If no results show up, the API server isn't bound to this port (or isn't running at all).
• Linux/macOS:
  Run:

  lsof -i :6443
  # Or alternatively
  netstat -tulpn | grep :6443
  

  You should see a process like kube-apiserver listening on the port.

4. Rule Out Firewall or Proxy Interference #

Sometimes local firewalls or proxy tools block the connection to port 6443:

• Windows: Temporarily disable Windows Defender Firewall (go to Settings > Update & Security > Windows Security > Firewall & Network Protection) and test kubectl version again. Don't forget to re-enable it after testing!
• Proxies/VPNs: If you're running a VPN, proxy client, or any network filtering tool, try turning it off temporarily. Kubectl might be routing traffic through the proxy instead of connecting directly to your local cluster.

After working through these steps, re-run kubectl version—it should successfully connect to the server and show both client and server versions.

内容的提问来源于stack exchange，提问作者lse23