https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# harvester
a
This message was deleted.
b
You can specify interface + VLAN for management traffic when installing Harvester. For Longhorn, you can configure a storage network for it to use if you want that separate from the management traffic
I'm not sure if you're installing via PXE or not, but you can configure all of these things as part of the PXE install, or after any installation method in the Settings page of the dashboard
b
Yes, I see that. I accomplished that fine, it’s clearer now. So, the mgmt network is cluster specific traffic. The harvester VIP though, I’d like to put on the public network. There was no option for interface for that one.
Actually, I can specific the hw_addr of the intstall vip. that may be it
b
No, you want the VIP hw_addr to be unique on the network. It's a load balancer for the k8s api servers. It uses layer 2 gratuitous ARPing to fail over to a new host. For example, if you have 3 harvester nodes, and 1 goes down, the VIP will float over to a new host's management interface and it will gratuitous ARP so that traffic sent to the VIP gets sent to the correct host
b
gotcha
that makes more sense
thank you!
🙂 1
Hrm. The thing here is that when I specify the mgmt network to be on the private LAN I mentioned before, then harvester cannot install as it tries to use the private network to access images it needs from the net and there is no gateway by design. It would be ideal to allow it to access net through public interface for install through an option
I may have figured it out by setting “default_route: false” in the mgmt interface. Thx! 😉
Open in Slack
PreviousNext
Powered by