System requirements
Requirements for the on-premises preview (the latest release). These are preview requirements, not certified production support minimums.
CloudGrange is one Helm chart. The installer paths build a K3s cluster and run it. With bring your own Kubernetes, you run it on your own cluster. The detailed, per-path requirements are in Prerequisites. This page summarises them.
Chart resource totals
These come from the chart's own requests, limits and volume claims, and cover CloudGrange's workloads only.
| Profile | CPU requests | Memory requests | Memory limits | Volumes (ReadWriteOnce) |
|---|---|---|---|---|
Installer paths (single-node) |
870m | 1.75 GiB | about 5.4 GiB | 6 volumes, about 21.4 GiB |
| Bring your own Kubernetes (default) | 870m | 1.75 GiB | about 5.4 GiB | 7 volumes, about 29.4 GiB |
multi-node |
1470m | 2.6 GiB | 8.5 GiB | 9 volumes, about 50.4 GiB |
The database, Prometheus and Loki volumes grow with the number of managed hosts and with retention.
VMs the installers create
| Path | vCPU | Memory | Disk | OS and Kubernetes |
|---|---|---|---|---|
| Windows script | 4 | 8 GB static | 30 GB virtual disk; 64 GB free at the VHDX path | Ubuntu 24.04 LTS, K3s v1.36.4+k3s1 |
| VHDX appliance | 2 | 4 GB startup, 2–8 GB dynamic | The imported VHDX | Ubuntu 24.04 LTS, K3s v1.36.4+k3s1 in the K3s appliance build. The published 0.1.0-lab.1 appliance still runs the legacy Compose engine |
Per path
| Path | Key requirements | Details |
|---|---|---|
| Bring your own Kubernetes | A conformant cluster (tested on Kubernetes 1.36), Helm 3 with OCI support, an ingress controller, a LoadBalancer for the relay, a default ReadWriteOnce StorageClass, cert-manager or your own certificate, a privileged Pod Security namespace, and cluster-admin to install |
BYO Kubernetes |
| Linux script | A dedicated, fresh Ubuntu 24.04 LTS install used only for CloudGrange, amd64, root, curl and python3, free ports 80, 443, 6443 and 8443 |
Linux script |
| Windows script | Hyper-V, PowerShell 7 as Administrator, the OpenSSH client, qemu-img (or -InstallPinnedQemu), 64 GB free, internet access |
Windows script |
| VHDX appliance | Hyper-V with Generation 2 and Secure Boot, PowerShell 7 as Administrator, a virtual switch, and an IP plan. No internet needed to import | Appliance |
| Azure | Not yet a released path | Azure |
Managed hosts
Managed Hyper-V hosts use the CloudGrange Windows service agent. The current agent guide covers Windows Server 2019, 2022 and 2025. WSFC is not a prerequisite for installing the control plane.
Network
| Port | Direction | Purpose |
|---|---|---|
| 443/tcp | Users to the ingress | Portal, API and the cloudgrange sign-in realm |
| 8443/tcp | Managed hosts to the relay | Agent connections, through the relay's LoadBalancer Service |
| 6443/tcp | Local to the K3s node | The Kubernetes API on the installer paths. Not a CloudGrange service |
The relay reaches the control plane over outbound HTTPS (443).