Hi，k3s master node will access itself's 6443 with Public IP(I setup the master with option --node-external-ip 1.2.3.4 as I has some cross-network nodes) ➜ ~ ss -antp dst 1.2.3.4 State Recv-Q Send-Q Local Address:Port Peer Address:Port Process ESTAB 0 0 192.168.0.153:52288 1.2.3.4:6443 users:(("k3s-server",pid=2027176,fd=191)) ESTAB 0 1702 [::ffff:192.168.0.153]:6443 [::ffff:1.2.3.4]:11179 users:(("k3s-server",pid=2027176,fd=157)) ESTAB 0 0 [::ffff:192.168.0.153]:6443 [::ffff:1.2.3.4]:52288 users:(("k3s-server",pid=2027176,fd=268)) How do I avoid this? Thank you :)

yeah, it’ll do that. Need to make sure it can access itself at its own IPs.

@creamy-pencil-82913 If so, there should be very little traffic usage for these connections(just for probing), right?