Hey everyone! I've been trying to convert my Docker Swarm home lab into a k3s cluster and I'm giving kube-vip a shot for handling virtual IPs. I have three Raspberry Pi 4s running Raspberry Pi OS Lite, and I'm hoping to have one act as the server and the other two as worker nodes. The issue arises when I add the second server node; it seems to create some ARP confusion, where the IP address I set for the second node is showing up as belonging to the first one. If anybody can help me spot the error in my configuration or installation steps, I'd really appreciate it! I've tried looking through the relevant docs but I'm not quite getting it.
2 Answers
Kube-vip can be tricky, especially with multiple nodes. Double-check your DaemonSet configuration across all nodes. They should all be running the kube-vip daemon properly, but it might help to see if there are any logs or errors when you deploy it on the second node. Also, make sure that the `K3S_TOKEN` is set correctly when you bootstrap the second node, as an incorrect token can sometimes lead to cluster issues. Check the configuration for typos too!
It sounds like you might be having troubles with the ARP setup between your nodes. One thing to check is whether both nodes have the correct configuration in their kube-vip settings. Make sure each node is assigned a unique address and that `kube-vip` is properly configured on both. You could also look into ARP settings on your local network to ensure it's not misrouting. Definitely check out the kube-vip GitHub page for more specific details regarding networking setups!
Thanks for the tips! I'll go through the configurations again and ensure that all settings are aligned. I really appreciate the help!