Prerequisites
These requirements apply to the on-premises preview (the latest release). They are preview requirements, not certified production support minimums.
CloudGrange is in active development and is not GA. See current product and release status.
How CloudGrange is delivered
The Helm chart is the product. Every delivery path installs the same CloudGrange Helm chart, with the same images. The paths differ only in who provides the Kubernetes cluster underneath it.
- Installer paths (the VHDX appliance, the Windows script and the Linux script) exist for customers who are not Linux or Kubernetes administrators. They build a host and a K3s cluster, then run the chart. They do nothing that the chart does not also do on your own cluster.
- Bring your own Kubernetes is for advanced customers who already run clusters. You install the chart with Helm.
What sits under the chart is the Foundation: the operating system and Kubernetes. The chart itself is the Platform. They are separate layers with separate updates. See the glossary and Support boundary.
Choose a path
| Path | You provide | CloudGrange provisions | Foundation | Prerequisites |
|---|---|---|---|---|
| VHDX appliance | A Hyper-V host | An Ubuntu VM with K3s, the chart and every image already inside | Managed | Appliance prerequisites |
| Windows script | A Windows Hyper-V host | An Ubuntu VM, K3s and the chart | Managed | Windows script prerequisites |
| Linux script | A dedicated, fresh Ubuntu server used only for CloudGrange | K3s and the chart | Managed | Linux script prerequisites |
| Bring your own Kubernetes | A Kubernetes cluster | The chart only | Customer | BYO Kubernetes prerequisites |
| Azure (AKS, VM, Container Apps) | An Azure subscription | Depends on the path | Azure + customer (AKS, Container Apps), managed (VM) | Azure prerequisites |
Managed: if you ran any CloudGrange installer, CloudGrange owns the Foundation, including operating-system updates, which your administrator starts from the Foundation card. Customer: only when you install the chart with helm directly on your own cluster do you own and upgrade Kubernetes yourself. On AKS and Azure Container Apps, Azure and you own it. See Updates.
What every path needs
These come from the chart and apply wherever it runs:
| Need | Detail |
|---|---|
| Compute | CloudGrange's workloads request 870m CPU and 1.75 GiB memory. Their memory limits total about 5.4 GiB. The installer paths create VMs with 4 vCPU and 8 GB (Windows script), or 2 vCPU and 4–8 GB dynamic memory (appliance) |
| Storage | ReadWriteOnce volumes: about 21.4 GiB on the installer paths, about 29.4 GiB with bring your own Kubernetes (default profile). See Storage |
| Network in | TCP 443 (portal, API and sign-in) from users. TCP 8443 (relay) from each managed Hyper-V host |
| Network out | ghcr.io, docker.io and quay.io for images, unless you use an offline bundle or the appliance. See Network egress |
| DNS | A DNS name for the portal (recommended), or an IP address. See DNS |
Managed hosts
The CloudGrange agent runs as a Windows service on each Hyper-V host you manage. The current agent guidance accepts Windows Server 2019, 2022 and 2025. See Install the CloudGrange Agent.
Managed hosts connect to the site relay on TCP 8443. The relay connects to the control plane over outbound HTTPS (443).
For the installer-synced summary, see the system requirements.