Glossary
The terms CloudGrange uses to describe how it is delivered, run and updated.
CloudGrange is in active development and is not GA. See current product and release status.
| Term | Meaning | Examples | Who owns it |
|---|---|---|---|
| Platform | The CloudGrange Helm release: our services, their images, the database schema and your data in it | The API, portal, identity (Keycloak), relay and PostgreSQL | CloudGrange, on every delivery path |
| Foundation | Everything below the Platform: the host operating system, the Kubernetes distribution, the container runtime, host services, and network and disk configuration | Ubuntu, K3s, containerd | CloudGrange whenever you used a CloudGrange installer, including OS updates. You, when you installed with helm directly. Azure and you on AKS and Azure Container Apps |
| Managed foundation | A Foundation built by a CloudGrange installer. If you ran any CloudGrange installer, CloudGrange owns the Foundation | The VHDX appliance, the Windows script, the Linux script, the Azure VM path | CloudGrange owns it, including OS updates through the Foundation card. Your administrator starts each update |
| Customer foundation | A Kubernetes cluster where you installed the chart with helm directly, or a platform Azure runs |
Your own Kubernetes cluster; AKS and Azure Container Apps | You, with helm directly. Azure and you on AKS and Azure Container Apps |
| Module | An add-on installed onto the Platform at run time | Hello World, AVD, FinOps | CloudGrange or the module's author |
| Delivery path | A way to get a running Platform | The VHDX appliance, the Windows script, the Linux script, bring your own Kubernetes, AKS, the Azure VM path | — |
| Wrapper (installer path) | The part of a delivery path that provisions a host and Kubernetes before it runs the Helm chart. A wrapper never does Platform work itself | Install-CloudGrange.ps1, Install-CloudGrange-Linux.sh, the VHDX appliance |
CloudGrange |
| Platform update | Moving the Platform from one release to another | New chart and image versions, database migrations | Offered in the portal on every delivery path |
| Foundation update | Patching or upgrading the operating system or Kubernetes under the Platform. Always started by an administrator | Ubuntu security patches, a new K3s version | Offered only on managed foundations |
Related terms
| Term | Meaning |
|---|---|
| Helm chart | The package that installs the Platform: oci://ghcr.io/cloudgrange/charts/cloudgrange. Every delivery path installs the same chart. The chart is the product |
| Bring your own Kubernetes (BYO) | Installing the chart with Helm on a cluster you already run. For advanced customers who operate Kubernetes. See BYO Kubernetes prerequisites |
| K3s | The lightweight, CNCF-conformant Kubernetes distribution that CloudGrange installs on managed foundations |
| Relay | The Platform service that CloudGrange agents on your Hyper-V hosts connect to, on TCP 8443 |
| Agent | The Windows service on each managed Hyper-V host |
| Foundation release | A signed, versioned set of Foundation changes (for example F2609.1.0), released separately from Platform releases. It declares its K3s version and the Platform versions it supports |
| Supported Kubernetes range | The Kubernetes versions a Platform release runs on. The chart declares it, and the portal shows whether your cluster is in range |
See Support boundary and Updates.