Skip to content

Kubernetes & Containers

Three container-platform services — managed clusters, registry, and serverless.

When to pick which

Workload pattern Pick
Long-running microservices, full K8s API Managed Kubernetes
Bursty HTTP API, no infra ops appetite Serverless Containers
Build/test pipelines pushing images Container Registry (always)
K8s with custom CRDs / operators / GPUs Managed Kubernetes + GPU VMs node pool

What "managed" covers

Component Managed by Cloud Digit
Control plane etcd, API server, scheduler, controller-manager (HA)
System addons CoreDNS, CNI, ingress controller (NGINX or Traefik), metrics-server
Patching K8s minor-version upgrades inside your maintenance window
Worker nodes OS patching is automated; node pools you size and choose
Workloads Yours — manifests, Helm charts, GitOps, RBAC inside the cluster

Cluster sizing baseline

Tier Control plane Worker pool size Best for
Dev / staging HA (3 nodes) 2 × small Pre-prod, internal tools
Production HA (3 nodes) 3 × medium minimum Customer-facing apps
Regulated HA (3 nodes), dedicated control plane 3 × medium + isolated node groups FI / regulated workloads

See Managed Kubernetes for full sizing and SLAs.