Score:0

Why is MetalLB automatically routing node ip to an specific service ip?

au flag

I'm trying to run PiHole on a k3s cluster inside my Raspberry Pi.

I have created a k3s cluster inside the RaspBerry Pi with only 1 node (the RaspBerry Pi itself). I also created a PiHole pod and a loadbalancer service. The loadbalancer uses MetalLB to create an external IP(192.168.68.11) with a Layer 2 Protocol.

So, as of now my set up has:

  1. Windows PC with an IP of 192.168.0.11
  2. Raspberry Pi with an IP of 192.168.0.16
  3. PiHole Load Balancer with an External IP of 192.168.68.11

Then:

  1. Pinging from the Raspberry to 192.168.68.11:8000 works as expected
  2. Pinging from the Windows PC to 192.168.68.11:8000 fails.
  3. Pinging from the Windows PC to 192.168.0.16:8000 works and it connects me to the PiHole Ui.

So my question is:

  1. How does MetalILB knows it has to route packages from the Node IP (192.168.0.16) to the Load Balancer that connects to the PiHole Service on 8000 port?
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.