This message was deleted.
# k3sa
adamant-kite-43734
09/25/2024, 2:36 PMThis message was deleted.
c
creamy-pencil-82913
09/25/2024, 2:52 PMYou can only add one additional server at a time. They should retry until the previous one finishes joining. Check the logs for progress.
creamy-pencil-82913
09/25/2024, 2:52 PMIf they never finish, check your etcd ports to make sure they can reach each other
p
proud-dentist-68957
09/25/2024, 3:40 PMThe etcd ports reachable (tested with telnet). I hope I won't bother too much by providing a bit of info and logs, so thanks in advance... Here's what I did:
I initialized the cluster on the first node (10.9.8.21), set up kube-vip in it with a virtual ip of 10.9.8.20 and tls-san for that address.
Waited approximately 20 minutes and then tried to join the second node (10.9.8.23) which resulted in a failure. Here's the journalctl from both nodes:
proud-dentist-68957
09/25/2024, 9:08 PMTurns out that the second network interface (eth1) on each node was interfering despite setting the flannel iface to eth0 and node-ip…
Once I recreated them up without the second interface and installed k3s there was no issue. Now I need to figure out how to make it work with both interfaces :)
6 Views