We have built a Proxmox single-node using an AMD NUC computer for testing and learning purposes. The hardware configuration for this system is as follows:
- GMKtec K8 Plus Mini PC, AMD Ryzen 7 8845HS processor with 8 C/ 16T, up to 5.1GHz with 1 TB MVNe SSD
- Crucial 96GB DDR5 RAM 5600MHz Memory upgrade
- 2TB SAMSUNG 990 EVO Plus M.2 MVNe SSD as a second drive
- M.2 SSD 5mm Low-Profile Heat Sink for the second NVMe
- Two Plugable 2.5GB USB-C Ethernet Adapters for additional Network Interfaces
Proxmox Installation/ZFS Storage
Proxmox installation is straightforward. We used the same procedure as our Production Cluster. The two NVMe drives were configured as follows:
- 1 TB NVMe – ZFS Formatted Boot pool named rpool
- 2 TB NVMe – ZFS Formatted pool named zfsa, mount point zfsa_mp
Networking Configuration
| Virtual Bridge | Purpose | VLAN | Speed | Adapter |
|---|---|---|---|---|
| vmbr0 (Mgmt) | Proxmox Management | Computers | 2.5 GbE | LAN #2 on NUC |
| vmbr1 (LS Svcs) | Low-Speed Services | All VLANs | 500 Mbps | LAN #1 on NUC |
| vmbr2 (HS Svcs) | High-Speed Services | All VLANs | 2.5 GbE | USB-C Adapter #1 |
| vmbr3 (Storage) | HA Storage for VMs/LXCs | Storage | 2.5 GbE | USB-C Adapter #2 |
The Networking configuration on our test node mirrors the setup in our Production Cluster. The table above outlines the Test Node networking setup. We could not configure one of the ports on the host system to operate above 500 Mbps.
Storage Configuration
The table above shows the storage configuration for our Test Node. NUC-storage is implemented on our high-availability NAS. Access is provided to both the Production Cluster and NUC Proxmox Backup Server datastores (more info here).
Proxmox Backup Server Configuration
Backups for our Test Node mirror the configuration and scheduling of Backups on our production Cluster (more info here).
Additional Configuration
The following additional items are configured for our test node:
- Use of No Subscription Repository
- SSL Certificate from Lets Encrypt
- Postfix for e-mail forwarding
- Clock sync via NTP
- Monitoring via built-in Influxdb and Grafana