Format:
Export:

Prerequisites & cluster preparation(15 of 15)

Keep this order!
⚠️ Cluster introduction

The following tests have been executed on a Single Node OpenShift (SNO) cluster.

The cluster is using: Minio Object Storage, MetalLB, LVM (local disks must be available), and a single NIC (a 2nd IP address is used for the VM network tests).

Some test cases could not be fully executed due to limitation of the SNO cluster or the hardware. They are still documented for reference and marked accordingly.

A NodeNetworkConfigurationPolicy (NNCP) is a Kubernetes resource that tells the NMState Operator how the node network should be configured — persistently, including after reboot. On this (Hetzner) server, variant A is used: three pure software bridges without a physical uplink. eno2 is controlled by OVN-K/OVS and must not be used directly as a bridge port.

1✅ Current variant: A — software bridges (br-net1, br-net2, br-net3)
2What do the three bridges do? → Three isolated virtual switches on the node
br-net1 = network 1 (e.g. application VMs)
br-net2 = network 2 (e.g. database VMs)
br-net3 = network 3 (e.g. storage/backup VMs)
3VMs on the same bridge can communicate — VMs on different bridges are isolated
4No traffic leaves the node — external access only via MetalLB/masquerade on eno2/br-ex
5Apply NNCP: oc apply -f sno-software-bridges.yaml
6Track status: watch oc get nnce (wait until Available)
7Verify bridges on the node using the commands in the Commands / YAML tab
8Critical: br-ex / eno2 node IP must be unchanged after apply!