Fleet Overview
Hypervisor Nodes
2
KubeVirt-capable cluster members
Cluster RAM
125 GiB
Total allocatable memory
Cluster CPU
64 Threads
Total allocatable threads
ContainerDisk Builds (7d)
657
1296 builds all-time
Hypervisor Capacity
Installed RAM and CPU threads per KubeVirt-capable node. Actual VM packing is constrained by k8s scheduler requests and the qa-vm-fleet template semaphore.
Cluster aggregate capacity derived from docs/data/factory-stats.json factory.cluster.nodes.
Guest Filesystems
Distribution of root filesystems across the published containerDisk catalog. Values reflect the filesystem selected by bootc install-to-disk or the upstream image, not the host format.
Filesystem mapping sourced from argo/workflow-templates/build-containerdisk.yaml and provision-flatcar-vm.yaml.
ContainerDisk Inventory
Published VM boot images in the local Zot registry. Sizes are OCI layer sizes; the raw disk unpacked inside the virt-launcher pod is larger.
Hypervisor Nodes
KubeVirt-capable cluster nodes that can schedule test VM workloads.
Provisioning Architecture
Test VMs boot from OCI containerDisk images stored in the local Zot registry (192.168.1.102:30500). Each pipeline run pulls the disk image and launches a fresh KubeVirt VM. The VM is torn down on exit.
- ContainerDisk VMs schedule on any KubeVirt-capable node; PVC-backed lanes co-schedule on the PVC node.
- Bluefin non-LTS uses btrfs; Bluefin LTS uses xfs; Flatcar uses ext4.
- SSH keys are injected at runtime via KubeVirt accessCredentials; no key material is baked into images.
Provenance: node capacity and containerDisk build counts from docs/data/factory-stats.json; disk catalog live-polled from ghost Zot (fallback marks unavailable).Raw dataset