Connecting a virtual machine to a Linux bridge network

In the web console, click Networking → Network Attachment Definitions.

click Create Network Attachment Definition.

Enter a unique Name and optional Description.

click the Network Type list and select CNV Linux bridge.

Enter the name of the bridge in the Bridge Name field.

Optional: If the resource has VLAN IDs configured, enter the ID numbers in the VLAN Tag Number field.

Optional: Select MAC Spoof Check to enable MAC spoof filtering. This feature provides security against a MAC spoofing attack by allowing only a single MAC address to exit the pod.

click Create.

Create a network attachment definition in the same namespace as the virtual machine.

Add the virtual machine to the network attachment definition, as in the following example:

apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
  name: <bridge-network> (1)
  annotations:
    k8s.v1.cni.cncf.io/resourceName: bridge.network.kubevirt.io/<bridge-interface> (2)
spec:
  config: '{
    "cniVersion": "0.3.1",
    "name": "<bridge-network>", (3)
    "type": "cnv-bridge", (4)
    "bridge": "<bridge-interface>", (5)
    "macspoofchk": true, (6)
    "vlan": 1 (7)
  }'

Create the network attachment definition:

$ oc create -f <network-attachment-definition.yaml> (1)

In the correct project in the OKD Virtualization console, click Workloads → Virtualization from the side menu.

click the Virtual Machines tab.

Select a virtual machine to open the Virtual Machine Overview screen.

click Network Interfaces to display the NICs already attached to the virtual machine.

click Add Network Interface to create a new slot in the list.

Use the Network drop-down list to select the network attachment definition for the additional network.

Fill in the Name, Model, Type, and MAC Address for the new NIC.

click Add to save and attach the NIC to the virtual machine.

Create or edit a configuration of a virtual machine that you want to connect to the bridge network.

Add the bridge interface to the spec.template.spec.domain.devices.interfaces list and the network attachment definition to the spec.template.spec.networks list. This example adds a bridge interface called bridge-net that connects to the a-bridge-network network attachment definition:

apiVersion: kubevirt.io/v1
kind: VirtualMachine
metadata:
    name: <example-vm>
spec:
  template:
    spec:
      domain:
        devices:
          interfaces:
            - masquerade: {}
              name: <default>
            - bridge: {}
              name: <bridge-net> (1)
...
      networks:
        - name: <default>
          pod: {}
        - name: <bridge-net> (2)
          multus:
            networkName: <network-namespace>/<a-bridge-network> (3)
...

Apply the configuration:

$ oc apply -f <example-vm.yaml>

Optional: If you edited a running virtual machine, you must restart it for the changes to take effect.