This message was deleted.

I have 3 k3s server nodes:

# kubectl get node | grep erver
k3d-k3s-default-server-0   Ready    control-plane,etcd,master
k3d-k3s-default-server-1   Ready    control-plane,etcd,master
k3d-k3s-default-server-2   Ready    control-plane,etcd,master

And there’s one etcd runs directly at host port 2379:

# netstat -nplt | grep 2379
tcp        0      0 <http://145.xxx.xxx.xxx:2379|145.xxx.xxx.xxx:2379>       0.0.0.0:*               LISTEN      2229051/k3s server
tcp        0      0 127.0.0.1:2379          0.0.0.0:*               LISTEN      2229051/k3s server

The pods data seems out-dated to me, and I wonder what should

ETCDCTL_ENDPOINTS

be?