Hi, I habe problems with Harvester Load Balancer, ...
# harvester
g
Hi, I habe problems with Harvester Load Balancer, and I don’t know if I am using it correctly. I am running it on OVH with a single bonded NIC connected to the vRack. That one bond carries both the private DHCP network (172.16.x.x/16) and a routed public IP (/30). I can make either the private network work or the public network work, but not both reliably at the same time. Right now I’m trying to add the public default route in netplan on the guest VM, but then internal traffic breaks. If I rely only on the private DHCP gateway, then the public traffic breaks. I can’t get the routing rules to correctly separate local vs. public paths. Has anyone solved this on Harvester with a single bond for both public and private traffic? How did you cleanly route internal traffic to stay local while sending public traffic through the OVH gateway? Any working configuration examples or guidance would be really helpful. As far as I know, Harvester LB does not support multiple interfaces selection, so maybe I should switch to something like MetalLB and try with two separate networks? Or maybe proper routing tables are enough. Is it ok to use untagged network, or should I use VLAN 1 for VMS?
The best what I have now is: Default (local) routing through DHCP, additional ARP broadcast and routes using netplan:
Copy code
network:
  version: 2
  ethernets:
    enp1s0:
      dhcp4: true
      addresses:
        - 57.130.34.105/30
      routes:
        - to: default
          via: 57.130.34.106
This partially works with:
Copy code
net.ipv4.conf.all.rp_filter=2
net.ipv4.conf.enp1s0.rp_filter=2
It does not work for new services, works for existing LB and local connectivity. It looks like the best pratice would be to separete public/private into separate NICs, right?
b
Hi @gorgeous-guitar-43479, thanks for reaching out. Yes, I think it's generally a cleaner solution to separate public/private into separate NICs.
g
Thanks for the response. That would only require to setup two NIC, one configured with DHCP (lets say vlan10) for vms, and one for public networking (public - has to be untagged or 1) during K8S creation from Rancher? https://github.com/harvester/harvester/issues/7500 This also means that I need to use other LB, as embedded one is not aupporting secondary nics right?
I think I may try to use MetalLB or CiliumLB with L2 adv, both have interface selection in the configuration.
After playing with it for two days, the easiest/safest/most reliable solution is to use OpenStack lb which i can configure with my bare metal.
👍 2