Managing Virtual Machines with Red Hat OpenShift Virtualization

To review the current network state for a particular node, use the oc get nns/node-name -o yaml command or the Networking → NodeNetworkState page.

A Node Network Configuration Policy resource is a YAML manifest that describes the intended network configuration for Red Hat OpenShift nodes, and is applied to all nodes in the cluster by default.

OpenShift Virtualization supports managing the Linux bridge, VLAN, Ethernet, and bond interface types.

To remove an interface from a node, you must modify or create an NNCP that designates the interface as absent under the state parameter.

OpenShift Virtualization uses the Multus CNI plug-ins and the Kubernetes NMState Operator resources to create a Linux bridge that connects VMs to additional networks.

Additional network interfaces that use the Multus CNI plug-in follow the netN naming convention.

If the VM requires a static or dynamic IP address, you must attach a secondary network interface to a bridge network to your VM.

You use a network attachment definition to connect a VM to a bridge network.

You can verify the network attachment definition in a namespace with the oc get net-attach-def -n namespace command or the Networking → Network Attachment Definitions page.

A DHCP server must be available on the bridge network to provide a dynamic IP address to VMs.

Use the cloud-init service to specify a static IP address for a secondary interface.