adamant-kite-43734
11/05/2024, 11:48 AMvictorious-photographer-77380
11/05/2024, 11:52 AM[root@dal3-qz2-sr3-rk247-s02 ~]# etcdctl --endpoints=<http://10.22.67.25:2379> member list
2c5cd24cb05252b3, started, dal3-qz2-sr3-rk247-s02, <http://10.22.67.25:2380>, <http://10.22.67.25:2379>, false
54911b049ff9105c, started, dal3-qz2-sr3-rk247-s14, <http://10.22.67.27:2380>, <http://10.22.67.27:2379>, false
df0d018a06009a0e, started, dal3-qz2-sr3-rk247-s12, <http://10.22.67.26:2380>, <http://10.22.67.26:2379>, false
[root@dal3-qz2-sr3-rk247-s02 ~]# etcdctl --endpoints=<http://127.0.0.1:2379> member list
{"level":"warn","ts":"2024-11-05T11:52:11.867565Z","logger":"etcd-client","caller":"v3@v3.5.13/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"<etcd-endpoints://0xc000364000/127.0.0.1:2379>","attempt":0,"error":"rpc error: code = DeadlineExceeded desc = context deadline exceeded"}
Error: context deadline exceeded
victorious-photographer-77380
11/05/2024, 11:55 AMcontext deadline exceeded
error in k3s, I can see the endpoint URL it's using is 127.0.0.1
- does anyone happen to know if k3s
is using 127.0.0.1
to query the cluster internally?victorious-photographer-77380
11/05/2024, 12:19 PMnode-ip
or node-external-ip
?