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.

Kasten K10 is an enterprise backup/restore solution from Veeam with native KubeVirt support for OpenShift Virtualization. K10 uses CSI snapshots and can back up VMs consistently without a guest-agent dependency. The existing MinIO from PRE-11 is used as the S3 backend.

Important: the MinIO API Route uses a self-signed certificate — K10 must be configured for insecure S3. Veeam Kasten (Free) covers clusters up to 10 nodes (sufficient for SNO PoC). Helm install is documented as an alternative in the Commands/YAML tab.

1Create namespace kasten-io (if not created during operator install)
2OpenShift Console → Ecosystem → Software Catalog → Operators → search for Veeam Kasten → install Veeam Kasten (Free) (Certified)
3Namespace: kasten-io, channel: stable, approval: Automatic
4After the operator reaches Succeeded: Installed Operators → Veeam Kasten → Create instance (K10 CR)
5Use the YAML from the Commands/YAML tab — set global.persistence.storageClass: lvms-vg1, enable Route and token auth
6Wait for K10 pods in kasten-io (Running, takes 3–5 min)
7Open K10 dashboard via the operator-created Route (or oc port-forward — see Commands/YAML tab)
8Create MinIO bucket for K10: k10-backups — mc mb local/k10-backups --insecure
9Create location profile in K10 UI (S3-compatible, MinIO endpoint, insecure) — or apply the Profile CR from Commands/YAML
10Validate profile: status Valid / Connected
11Check K10 license (free tier active for SNO)
12Alternative: Helm install — see Alternative: Helm install section in Commands/YAML tab