Sorry, I’m novice here and in kubernetes 
I have a Kubernetes cluster with 1 server at the moment (5 in total eventually), using MetalLB in L2 mode to manage a virtual IP (x.x.x.100) as a LoadBalancer.
The virtual IP works fine on the first server (Server 1), but I’m facing an issue when trying to connect from a second server (Server 2).
On Server 1, I can access the virtual IP with curl http://x.x.x.100:80, and it returns a 200 status.
On Server 2, the same request fails with the error: curl: (7) Failed to connect to x.x.x.100 port 80.
Using the command arp -n, I noticed that the virtual IP 10.1.10.100 shows as “incomplete” on both servers, indicating that the MAC address associated with this IP isn’t resolved.
My cluster is using MetalLB with an IP pool (IPAddressPool) in L2 mode. I’ve checked the MetalLB configurations, and I suspect an issue with the propagation of the MAC address for the virtual IP between the nodes.
Do you have any suggestions or ideas to resolve this connectivity issue between the nodes?