|
For the latest version, please use Virtual Appliance 1.1.1! |
Hardware requirements
Reserve resources for Management and appliance nodes separately. Capacity depends on your workload and retention needs. Choose your deployment options in the Installation Introduction.
Tested hypervisors
The Management ISO VM and appliance nodes have been tested on these hypervisors:
| Hypervisor | Tested version | Appliance deployment guide |
|---|---|---|
Proxmox VE |
9 |
|
VMware vSphere |
9.1 |
This table records tested configurations only. It does not exclude other hypervisors or versions. For signed VMware media, validate the import, firmware trust and TPM settings on the intended host build.
Management
Both Management deployment options need the following resources:
| Resource | Minimum | Recommended |
|---|---|---|
CPU |
2 CPUs |
2 CPUs |
Memory |
4 GiB |
4 GiB |
Persistent storage |
50 GiB |
100 GiB |
Where the hypervisor uses MiB, configure 4096 MiB memory. In vSphere, select GB for Memory and enter the table’s GiB value.
For the Management ISO VM, use AMD64 virtual CPUs and one dedicated state disk. Keep the Management ISO attached and first in boot order for every boot. The state disk holds persistent host settings, Management data, credentials, images and logs. Allow space for bundle imports and operations and keep the disk access-controlled because it contains secrets. See Management capacity and cleanup for the free-space thresholds that pause new work.
For Docker or Docker Compose,
reserve that capacity in the engine’s storage and mount a persistent volume at /var.
Host and container-runtime overhead is additional.
Choose the native image variant for the engine
and check the minimum runtime versions.
Appliance nodes
Choose Standalone for one node or Three nodes for three nodes. Standalone has no node redundancy.
| Requirement | Required configuration |
|---|---|
Firmware |
UEFI before the first boot, with Secure Boot enabled and verified before target discovery. |
TPM |
Persistent TPM 2.0. |
CPU features |
AES support on the host and exposed to the guest CPU as the |
Boot media |
The release’s signed noCloud ISO for Proxmox or signed Metal OVA for VMware. |
Disks |
Three separate writable disks for OS, Database and Data. Put the OS disk first in the boot order. |
| Keep the TPM and EFI state with the installed disks. Replacing either can prevent encrypted volumes from unlocking. |
| Per appliance node | Minimum | Recommended |
|---|---|---|
Virtual CPUs |
4 |
8 |
Memory |
16 GiB |
32 GiB |
OS disk |
80 GiB |
135 GiB |
Database disk |
10 GiB |
200 GiB |
Data disk |
10 GiB |
500 GiB |
Where the hypervisor uses MiB, configure at least 16384 MiB memory or the recommended 32768 MiB. In vSphere, select GB for Memory and disk capacity, and enter the table’s GiB values. Management accepts appliance disks at these minima. Workload volume, retained backups, metrics and logs can require more storage than these starting values. Management discovers eligible disks and requires one distinct disk for each role. It cannot use a single disk for several roles.
Minimum and recommended sizes use the same appliance service defaults. The recommended size provides more capacity for workload and recovery activity; it does not select a separate tuning profile or guarantee a particular transaction rate.
The recommended VMware OVA template supplies the recommended CPU, memory and disk allocations from the table above, with EFI firmware. The system disk contains the Talos boot image and offline installer cache and is the OS installation target. The Database and Data disks are empty. Use the three supplied disks for their respective roles in Management. Use the signed Metal OVA supplied for the selected release. It requires vCenter with a configured key provider and a fresh vTPM. Keep the populated OVA boot disk assigned to the OS role even if Management offers it for a data role. For Proxmox, retain the separate EFI and TPM state disks required by the VM configuration. See the Proxmox and VMware deployment steps.
Next step
Reserve the IP addresses and DNS names for Management and the Appliance.