[QUESTION/HELP] E0120 11:23:24.665782 6485 memcache.go:265] 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? getting this error in agent please help #1399

You didn't gave us enough information.

• What command are you trying to run ?

• Is the cluster running ? To find out:

  k3d cluster list kubectl cluster-info

• Is it actually running on the correct port, as said by the error ? Look at the kubeconfig file:

  kubectl config view.

@HarimbolaSantatra for listing cluster k3d cluster list using this command was getting this but at that time i didnt created any cluster so i should be getting any error it should so empty or something instead of this issue i guess?

Run the cluster first: k3d cluster create mycluster

I'm experiencing the same issue when running Colima on macOS. The problem seems to occur only in the agent nodes, which continuously spam the message:

E0304 07:50:34.464074    2885 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get     │
│local 2310ed54527ecb2e0aa434c5fd5d9ea1202837afa7c4ba35415fad9││\"http://localhost:8080/api?timeout=32s\": dial tcp [::1]:8080: connect: connection refused"

The cluster config is:

---
# yaml-language-server: $schema=https://raw.githubusercontent.com/k3d-io/k3d/refs/heads/main/pkg/config/v1alpha5/schema.json
apiVersion: k3d.io/v1alpha5
kind: Simple
metadata:
  name: lab-config
image: rancher/k3s:latest
kubeAPI:
  hostPort: "6443"
servers: 1
agents: 2
options:
  k3s:
    extraArgs:
      - arg: --disable=local-storage
        nodeFilters:
          - server:*
      - arg: --disable=traefik
        nodeFilters:
          - server:*
      - arg: --disable=metrics-server
        nodeFilters:
          - server:*
      - arg: --disable=coredns
        nodeFilters:
          - server:*
      - arg: --disable=servicelb
        nodeFilters:
          - server:*
      - arg: --flannel-backend=none
        nodeFilters:
          - server:*
      - arg: --disable-network-policy
        nodeFilters:
          - server:*
      - arg: --disable-kube-proxy
        nodeFilters:
          - server:*
      - arg: --disable-helm-controller
        nodeFilters:
          - server:*
  kubeconfig:
    updateDefaultKubeconfig: false
    switchCurrentContext: false

The creation logs:

INFO[0000] Using config file /Users/marcocondrache/Personal/lab-config/cluster.yaml (k3d.io/v1alpha5#simple)
INFO[0000] Prep: Network
INFO[0000] Created network 'k3d-lab-config'
INFO[0000] Created image volume k3d-lab-config-images
INFO[0000] Starting new tools node...
INFO[0000] Starting node 'k3d-lab-config-tools'
INFO[0001] Creating node 'k3d-lab-config-server-0'
INFO[0001] Creating node 'k3d-lab-config-agent-0'
INFO[0001] Creating node 'k3d-lab-config-agent-1'
INFO[0001] Creating LoadBalancer 'k3d-lab-config-serverlb'
INFO[0001] Using the k3d-tools node to gather environment information
INFO[0001] Starting new tools node...
INFO[0001] Starting node 'k3d-lab-config-tools'
INFO[0002] Starting cluster 'lab-config'
INFO[0002] Starting servers...
INFO[0002] Starting node 'k3d-lab-config-server-0'
INFO[0004] Starting agents...
INFO[0004] Starting node 'k3d-lab-config-agent-1'
INFO[0004] Starting node 'k3d-lab-config-agent-0'
INFO[0016] Starting helpers...
INFO[0016] Starting node 'k3d-lab-config-serverlb'
INFO[0022] Injecting records for hostAliases (incl. host.k3d.internal) and for 5 network members into CoreDNS configmap...
INFO[0024] Cluster 'lab-config' created successfully!
INFO[0024] You can now use it like this:
export KUBECONFIG=$(k3d kubeconfig write lab-config)
kubectl cluster-info