Skip to main content
Version: v0.3

Harvester Network

Harvester is built on top of Kubernetes and leverages its built-in CNI mechanism to provide the interface between network providers and its VM networks.

We have implemented the Harvester VLAN network based on the bridge CNI to provide a pure L2-mode network, that would bridge your VMs to the host network interface and can be connected using the physical switch for both internal and external network communication.

Moreover, the Harvester UI integrates the harvester-network-controller to provide user-friendly VLAN network configurations, e.g., to create and manage VLAN networks or to add a VLAN network to the VM.

Currently, Harvester supports two types of networks:

Management Network

Harvester uses flannel CNI as its default management network. It is a built-in network that can be used directly from the cluster. However, the management network IP is not persisted and will be changed after a VM reboot.

Additionally, users can leverage the Kubernetes service object to create a stable IP for your VMs with the management network.

VLAN Network

The Harvester network-controller leverages the multus and bridge CNI plugins to implement its customized L2 bridge VLAN network. It helps to connect your VMs to the host network interface and can be accessed from internal and external networks using the physical switch.

The below diagram illustrates how the VLAN network works in Harvester.

  • The Harvester network-controller creates a bridge for each node and a pair of veth for each VM to implement its VLAN network. The bridge acts as a switch to forward the network traffic from or to VMs and the veth pair is like the connected ports between VMs and the switch.
  • VMs within the same VLAN can communicate with each other, while the VMs from different VLANs can't.
  • The external switch ports connected to the hosts or other devices (such as the DHCP server) should be set as trunk or hybrid type and permit the specified VLANs.
  • Users can use VLAN with PVID (default 1) to communicate with any normal untagged traffic.

Enabling Default VLAN Network

Users can enable the VLAN network via Setting > VLAN and selecting a common physical NIC for the nodes as the default VLAN config .

It is recommended to choose a separate NIC for the VLAN other than the one used for the management network (i.e., harvester-mgmt) for better network performance and isolation.

  • Modifying the default VLAN network setting will not update the existing configured host network.
  • Harvester VLAN network supports bond interfaces, currently it can only be created automatically via PEX Boot Configuration. Users may also login to the node and create it manually.

Optional: Users can customize each node's VLAN network via the HOST > Network tab.

Create a VLAN Network

A new VLAN network can be created via the Advanced > Networks page and clicking the Create button.

  • Specify the name and VLAN ID that you want to create for the VLAN network.


Create a VM with VLAN Network

Users can now create a new VM using the above configured VLAN network,

  • Click the Create button on the Virtual Machines page.
  • Specify the required parameters and click the Networks tab.
  • Either configure the default network to be a VLAN network or select an additional network to add.

  • Only the first NIC will be enabled by default. Users can either choose to use a management network or a VLAN network.
  • You will need to select the Install guest agent option in the Advanced Options tab to get the VLAN network IP address from the Harvester UI.
  • Users can choose to add one or multiple network interface cards. Additional network interface card can be enabled by default via setting the cloud-init network data. E.g.,
version: 1
- type: physical
name: enp1s0 # name is varies upon OS image
- type: dhcp
- type: physical
name: enp2s0
- type: DHCP

For more detailed configs you may refer to the cloud-init network configs.

Configure DHCP servers on Networks

By default, the Harvester VLAN network would expect your router to provide a DHCP server that VMs can request and assign IP addresses automatically.

If you are running Harvester in a virtual environment that does not contain a DHCP server, you may consider deploying a DHCP server manually in a node or using a containerized method. Refer to this issue as an example.