https://rancher.com/ logo
#k3s
Title
# k3s
a

adamant-kite-43734

05/25/2023, 9:51 AM
This message was deleted.
f

flat-bird-89111

05/25/2023, 9:56 AM
I have 3 k3s server nodes:
Copy code
# 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:
Copy code
# 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?
Turned out the etcd was connected to another k3d cluster, issue solved!