Cluster sizes and reference¶
Cluster sizes¶
Clusters are offered in four standard sizes: small, medium, large, and XL. The size sets the cluster's worker capacity (CPU, memory, and node count). Each worker has 4 vCPU and 16 GiB RAM, and each worker group contains three workers.
| Size | Worker groups | Worker nodes | Nominal worker CPU | Nominal worker RAM |
|---|---|---|---|---|
| Small (Liten in the portal) | 1 | 3 | 12 vCPU | 48 GiB |
| Medium (Mellan in the portal) | 2 | 6 | 24 vCPU | 96 GiB |
| Large (Stor in the portal) | 3 | 9 | 36 vCPU | 144 GiB |
| XL | 4 | 12 | 48 vCPU | 192 GiB |
These are nominal resources across the worker nodes, not guaranteed schedulable capacity. The operating system, Kubernetes, networking, monitoring, and other platform services use some CPU and memory. Check Kubernetes allocatable resources after provisioning when planning workload requests and limits.
Every size also has three dedicated control-plane nodes. Their resources are not included in the table and are not available for customer workloads. An operations jump host is also part of the infrastructure but is not a Kubernetes node. Each worker has a 100 GB system disk for the operating system and container runtime; use persistent volumes or object storage for application data.
Pick a starting size when you order. Resizing adds a whole worker group at a time: three workers, 12 vCPU, and 48 GiB nominal RAM. Larger configurations than XL are available by agreement. If you are unsure which size fits, contact Sunet with an estimate of your workloads and we'll advise.
What's included with every cluster¶
- A managed Kubernetes control plane and worker nodes
- ArgoCD for GitOps
- Sealed Secrets for safely storing encrypted secret manifests in Git
- Gateway API and an external load balancer
- cert-manager for TLS
- Canonical SUNET-managed hostnames for the Kubernetes API and Argo CD
- Ongoing maintenance and updates of the underlying infrastructure
The optional portal field Argo CD DNS alias records a customer's
requested alias, such as argocd.example.org. It does not replace the
cluster's Kubernetes API hostname, and saving it does not activate DNS,
routing, or TLS. The customer must create a CNAME from the alias to
argocd.<cluster-slug>.k8s-prod.sunetvdc.se; see
Gateway API, TLS and DNS.
Billing¶
The base cluster is billed by size. Optional add-ons (block storage, object storage, backup, DNS management API) are billed in addition, at standard storage rates where applicable. See the Sunet website for current pricing.
Platform rules to remember¶
- Every workload must be drain-tolerant. See The drain and PodDisruptionBudget contract.
- Maintenance and node restarts happen without prior notice; the cluster as a whole stays up, but individual nodes may restart.
- Persistent volumes and object storage are not backed up by default.