It sounds like you're wondering if a single metal NIC will be too limiting and prevent you from having some VMs that are reachable from the internet and other VMs that are behind a private LB.
I don't think a single NIC will necessarily prevent you from doing that.
The VMs behind the private LB would need to be on a Harvester network, perhaps a tagged network/VLAN.
The exposed LB VM would have to have a public IP or be the target of a port forward from a public IP. This VM need to be on a Harvester network that's reachable by that method.
03/23/2023, 1:56 AM
Not concerned about the single NIC, and creating a VM exposed to the internet. I don’t have a VLAN switch, but I can create an untagged network. The issue is how do I configure the VMs to be on a private network, but allow the LB to still connect to them?
03/23/2023, 2:06 AM
My home lab doesn't have any metal VLANs available either. You've reminded me of a question I need to answer for myself too.
Do Harvester tagged networks require a VLAN metal switch, or is it a virtual-virtual-LAN?
I think it's the latter. I was confused at first because the VM I created on the tagged network showed a yellow pill like "DHCP failed", but then I learned that DHCP is not provided, and so there was no DHCP server on the same VLAN.
I will try it with a DHCP server to see if I can operate on the virtual Harvester-defined tagged network/VLAN.
Great news, it works.
No need for a "VLAN switch" at all. The VLAN is defined inside the Harvester network. It is necessary to provide a DHCP server or assign static addresses to interfaces in the network of type L2VlanNetwork.
Although DHCP worked I did not succeed at routing traffic from LAN to WAN through pfSense. I'm not sure yet whether it's a problem with the router configuration or a Harvester configuration.
03/23/2023, 5:18 AM
I am not using DHCP. I will be using static IPs, but in any case just seems difficult to create private subnets on Harvester
03/24/2023, 2:13 AM
I'm still having some difficulty with this too.
I found that packets transmitted in the untagged network were received in the tagged network, and vice versa. The VLAN had a DHCP server that was issuing leases to devices on the untagged network. It seems like that should not be possible.
This leads me to think the Ethernet frames are not isolated by Harvester. I'm still not certain whether it's necessary to have a VLAN-aware metal switch attached to the Harvester node's NIC.