Prerequisites & cluster preparation(15 of 26)

Show

0/15 completed0%

Verified on SNO (single NIC). Some related tests may be marked not runnable.

Cluster Health Check — Starting Point

Clarify network topology — I.e. software bridges (variant A)

On the first test server, only one physical NIC (eno2) is available and is fully attached to the OVS bridge br-ex by OVN-Kubernetes. All current tests therefore use variant A (software bridges). Variant C (Hetzner vSwitch) and variant B (on-premises trunk) are documented for future expansion.

1✅ Current decision: variant A — software bridges (br-net1, br-net2, br-net3)

2Reason: Hetzner SNO node has only one NIC (eno2), fully controlled by OVN-K / br-ex

3Reason: Hetzner vSwitch (VLAN 4000) tested — works technically, but requires a second server in the vSwitch

4Reason: on-premises trunk port (variant B) not possible — no switch access at Hetzner

5Variant A provides full VM network isolation on the node internally — sufficient for all planned tests

6Keep NIC names from PRE-01 handy: eno2 (altname enp7s0) — required for PRE-04

Install and verify NMState Operator

Configure Linux bridges via NMState (Hetzner: variant A — software bridges)

Install OpenShift Virtualization Operator

Set up LVM Storage Operator — storage for VMs

Pull secret, import golden image, prepare SSH keys

Create namespace vmtest and NetworkAttachmentDefinitions

Install MetalLB Operator and configure IP pools (3 options)

MCE + HyperShift for hosted control planes

Deploy MinIO (S3 object storage)

Install MTV (Migration Toolkit for Virtualization) Operator

Install OADP Operator and configure with MinIO (S3)

Install Advanced Cluster Management (ACM) v2.17

Install Kasten K10 (Veeam) Operator and configure with MinIO

/ open searchJ/K next / previous card? keyboard shortcutsEsc close panels

🔧 Prerequisites & cluster preparation(15 of 26)

Prerequisites & cluster preparation(15 of 26)