A three-node cluster is the standard starting point for production designs that require control-plane resilience, storage replication across hosts, and a target for live migration. Final topology and sizing depend on workload demand, growth, protection policy, and failure-reserve requirements.
Administrators / Rancher
|
NQRust UI / API / VIP
|
+-----------------------------------------------------------------------+
| Three-Node NQRust Hypervisor Cluster |
| |
| +------------------+ +------------------+ +------------------+ |
| | Node 1 | | Node 2 | | Node 3 | |
| | RKE2 + KVM | | RKE2 + KVM | | RKE2 + KVM | |
| | KubeVirt | | KubeVirt | | KubeVirt | |
| | Longhorn replica | | Longhorn replica | | Longhorn replica | |
| +------------------+ +------------------+ +------------------+ |
| <---- Cluster, storage replication, and migration network ----> |
+-----------------------------------------------------------------------+
| VM VLAN / trunk | Backup network
v v
Workload networks NFS or S3 target
Management, VM, storage, migration, and backup traffic can be separated according to security, performance, and availability requirements. The cluster should be sized so that the remaining nodes can carry critical workloads while one node is unavailable.