Kubernetes features and limits

_{Updated August 24, 2026}

Limits

Limit	Value
Clusters per account	10 (contact support to raise)
Node pools per cluster	unlimited; ≥1 required
Nodes per pool	2–20
Minimum workers per cluster	2
Storage nodes	0, 2 or 3; 10–1000 GB data disk each
MetalLB address pool	up to 32 addresses
Kubernetes versions	up to three minor versions with in-place upgrades — see Supported versions
Region	us-east
Connections / requests / Ingress hosts	No platform-imposed limits — throughput is bounded only by your cluster’s dedicated gateway capacity (per-cluster, unaffected by other tenants)

Managed, free control plane (optional 3-master HA), RKE2 + Cilium
Node pools with labels, taints and autoscaling (all pools share the cluster’s worker plan)
Drain-first scale-down (PodDisruptionBudgets honoured, never force-deleted)
Admin kubeconfig; full REST API; dashboard with workloads, pods, live logs, metrics and control-plane health
App Hub one-click installs with HTTPS/TCP expose
Dedicated VPC, gateway firewall (baseline or your security group), Traefik and MetalLB options, Longhorn storage nodes
99.90% monthly SLA (endpoint path on HA clusters) and 24/7 support

Honest list of gaps we’re working on:

Kubeconfig rotation / short-lived credentials — the kubeconfig is a long-lived admin credential; treat it accordingly
Multiple regions — us-east only
Windows nodes, GPU nodes, IPv6