Format:

Export:

Test cases(24 of 50)

Show

Priority

Category

0/24 completed0%

Complete prerequisites first ([PRE-01](PRE-01) → [PRE-08](PRE-08) minimum) before running these tests. Go to prerequisites

Verify golden image import and PVC clone

Create and boot first VM from template (RHEL 9)

Masquerade uses OVN-K over eno2/br-ex — no bridge setup required

VM live migration (SNO: expected failure)

NOT POSSIBLE on SNO — live migration requires ≥2 nodes. Documented as an expected failure.

Create VM snapshots and perform restore

Test on local storage

Clone VM and use as template (Golden VM pattern)

Pod network (masquerade) and VM access via Service

Optimal for single-NIC — OVN-K over eno2/br-ex, no bridge setup required

VM directly reachable on LAN (OVN-K localnet) -- ⚠ HETZNER TOS VIOLATION

✗ NOT TESTABLE ON HETZNER -- TOS violation! OVN-K localnet works technically (verified 30.06.2026: ping successful), but any VM MAC that reaches eno2/the physical switch via this interface is detected and reported by Hetzner as an unauthorised MAC (server suspension threatened). Only the registered server MAC is permitted.

SR-IOV – high-performance networking (HW missing)

✗ NOT TESTABLE — SR-IOV requires a dedicated second NIC (Intel X710, Mellanox ConnectX). The sole NIC eno2 is consumed by OVN-K and cannot be used for SR-IOV VFs.

Test VLAN isolation — VMs in separate software bridges

Variant A uses pure software bridges br-net1/2/3 (port: []) — no VM MAC leaves eno2/the physical switch, no TOS risk. Variant B (on-premises, trunk port) is relevant only with your own switch.

Inter-VLAN routing via router VM (br-net1 ↔ br-net2)

purely internal software bridges br-net1/br-net2 (port: []) — no VM MAC leaves the node

VM with 3 Network Interfaces (Management + Data + Storage)

OVN-Kubernetes UserDefinedNetwork (Layer2 Overlay)

UserDefinedNetwork with Layer2 topology is a pure overlay (encapsulated Geneve tunnel within OVN-K) — explicitly NOT localnet, so no VM MAC leaves the node.

⚠️ DEDICATED NAMESPACE REQUIRED: see NOTE below.

Verify MetalLB Basic Functionality

2 Pools: internal-pool binds to br-net1 — external-pool binds to eno2, requires a 2nd public IP

Verify MetalLB from PRE-09. Primary test runs via internal-pool (192.168.10.100-120, internal on br-net1) — immediately usable without waiting for an additional IP. Once a second Additional IP is available, additionally test Option 1 (external-pool, external).

Prerequisites checklist

Confirm these before running steps:

PRE-09Install MetalLB Operator and configure IP pools (3 options)
PRE-07Pull secret, import golden image, prepare SSH keys
For the external part optionally: second Hetzner Additional IP delivered

1Verify MetalLB components are Running

oc get pods -n metallb-system

→ controller-* and speaker-* (one speaker per node) must show Running with 1/1

2Verify IPAddressPool and L2Advertisement from PRE-09

oc get ipaddresspool -n metallb-system

oc get l2advertisement -n metallb-system

→ internal-pool (192.168.10.100-120, interface br-net1) must be present

3Apply test deployment (httpd) + LoadBalancer service (full block in the Commands / YAML tab)

4Wait until the pods are Running

oc get pods -n vmtest -l app=httpd-example -w

Press Ctrl+C once Running appears

5Watch EXTERNAL-IP of the service

oc get svc nginx-lb -n vmtest -w

→ EXTERNAL-IP changes from <pending> to an IP from 192.168.10.100-120 — typically under 10 seconds

Press Ctrl+C once the IP appears

oc get svc nginx-lb -n vmtest

oc describe svc nginx-lb -n vmtest

6Create test client VM on br-net1

7Wait until the VM is Running

watch oc get vmi curl-test-vm -n vmtest

8Wait for key propagation

sleep 30

9Log in via SSH, set IP on the second interface (no DHCP on br-net1), then test curl

virtctl ssh fedora@vm/curl-test-vm -n vmtest -i ~/.ssh/ocp-vm-key

sudo ip addr add 192.168.10.50/24 dev enp2s0 && sudo ip link set enp2s0 up

sleep 20

curl http://<external-ip>

→ httpd default page — the curl result alone already proves MetalLB works

102nd Test with public IP: once the second IP is available: repeat the same test with external-pool (Commands / YAML tab, section 'External variant') — then curl is also possible from your own laptop/internet

watch oc get svc nginx-lb-external -n vmtest

curl http://<external-ip>

11Clean up (optional):

oc delete deployment httpd-example -n vmtest

oc delete svc nginx-lb -n vmtest

oc delete svc nginx-lb-external -n vmtest

oc delete vm curl-test-vm -n vmtest

Expose VM Services via MetalLB (SSH)

external-pool uses a provider-registered additional IP (e.g. Hetzner Additional IP); MetalLB speaker announces with the node's own MAC.

⚠️ SHARED RESOURCE: external-pool currently has only ONE IP — Clean up after this test (delete vm-ssh-lb) before starting TC-HCP-002

MetalLB BGP Mode with Router Peering

⚠️ NOT usable by default on the current SNO cluster: there is no customer-controlled router in the path for peering. Left for documentation purposes and future tests.

Multiple IP Pools and Namespace Isolation

MetalLB + Isolated Software Bridges: LB IPs per Bridge Interface

L2Advertisement explicitly binds to br-net1/br-net2 — ARP announcements stay node-internal.

Verify HyperShift Operator and MCE

Single-NIC OK — HyperShift pods use the OVN-K pod network.

⚠️ Check Pod/Node Capacity before starting TC-HCP-002 — see steps below.

Create Hosted Cluster with KubeVirt provider

⚠️ SNO EXAMPLE INSTALLATION: --control-plane-availability-policy SingleReplica is mandatory on a single-node cluster.

Scale NodePool and change VM flavour

⚠️ Be sure enough compute resources are available on the SNO node before starting this test.

Remove Hosted Cluster cleanly (destroy)

DataVolume import from multiple sources

Import over OVN-K — bandwidth is shared with OCP traffic on eno2/br-ex in this cluster

Create VM backup with OADP

Restore VM from OADP backup

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

🧪 Test cases(24 of 50)

Test cases(24 of 50)