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

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

Separate IP pools per namespace/team. Security separation: services in namespace 'production' receive only IPs from the prod pool. Uses two sub-ranges of the internal br-net1 subnet from PRE-09.

Prerequisites checklist

Confirm these before running steps:

PRE-09Install MetalLB Operator and configure IP pools (3 options)
PRE-04Configure Linux bridges via NMState (Hetzner: variant A — software bridges)
Create namespaces production and development

1Create namespaces production and development with appropriate labels

oc new-project production && oc label ns production env=production

oc new-project development && oc label ns development env=development

2Apply two IP pools with namespaceSelectors + L2Advertisements (STEP 2 in the Commands / YAML tab — fully written out, no reference to other test cases required)

3Verify the pools are created

oc get ipaddresspool -n metallb-system

→ prod-pool (192.168.10.140-149) and dev-pool (192.168.10.150-159) must be listed

4Create test deployment and service in namespace production (STEP 3 in Commands / YAML tab)

5Verify the service is created

oc get svc nginx-lb -n production

→ EXTERNAL-IP must come from the .140–.149 range (automatic via namespaceSelector, no pool annotation required)

6Create test service in namespace development (STEP 4 in Commands / YAML tab)

7Verify the service is created

oc get svc nginx-lb -n development

→ EXTERNAL-IP must come from the .150–.159 range

8Negative test: service in production explicitly requests dev-pool

oc annotate svc nginx-lb -n production metallb.io/address-pool=dev-pool

oc get svc nginx-lb -n production

→ EXTERNAL-IP remains <pending>; isolation works correctly

9View events for error diagnosis

oc describe svc nginx-lb -n production

→ Events section shows the actual rejection reason, e.g. 'pool dev-pool not compatible for ip assignment'

10Clean up (optional)

oc delete project production development

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)