Skip to main content
K8sCalc

kubernetes

Kubernetes Cluster Cost Calculator

Calculate the monthly cost of running a self-managed Kubernetes cluster on Hetzner Cloud, Vultr, or DigitalOcean. Choose server types for control planes, workers, and load balancers with HA mode.

Content reviewed Jul 18, 2026Hetzner Cloud pricing synced live — Jul 24, 2026Vultr pricing synced live — Jul 24, 2026DigitalOcean pricing synced live — Jul 24, 2026

VPS & Cloud Hosting

We earn a commission when you sign up through the links below — at no extra cost to you.

Kubernetes Cluster Architecture on Hetzner Cloud

Hetzner Cloud is one of the most cost-effective platforms for self-managed Kubernetes clusters. A full HA production setup typically costs 4–10× less than managed Kubernetes on AWS or GKE.

Recommended Production Architecture

  • 3× Control Plane nodes (cpx32: 4 vCPU, 8 GB RAM) — etcd + kube-apiserver + kube-scheduler
  • 3+ Worker nodes (cpx42: 8 vCPU, 16 GB RAM) — your actual workloads
  • 2× HAProxy load balancer nodes (cpx22) with Keepalived Floating IP — HA for K8s API + Ingress
  • 1 Private network (10.20.0.0/24) — internal cluster communication

Why 3 Control Planes?

etcd requires a quorum of (n/2)+1 nodes to elect a leader and accept writes. With 3 nodes, you tolerate 1 failure. With 5, you tolerate 2. Running 2 control planes gives you no fault tolerance — if one fails, etcd loses quorum and the entire cluster becomes read-only.

Server Type Guide (eu-central, verified 2026-05)

TypevCPURAMMonthlyUse Case
cx232 shared4 GB€5.49LB / bastion
cx334 shared8 GB€8.49Control plane (budget)
cax214 ARM8 GB€10.49Control plane (ARM)
cx438 shared16 GB€15.99Worker (standard)
cax318 ARM16 GB€20.99Worker (ARM)
cx5316 shared32 GB€29.49Worker (large)
ccx234 ded.16 GB€85.99Worker (dedicated CPU)
ccx338 ded.32 GB€138.49Worker (dedicated, heavy)

Cost Optimization Tips

  • Use shared x86 (cx) rather than ARM (cax) if pure cost is the priority — cax currently costs more per core on Hetzner. Pick ARM only where its performance-per-core actually beats cx for your workload.
  • Enable Longhorn with S3 backup instead of using Hetzner Volumes (cheaper at scale)
  • Use the node autoscaler to scale workers down during off-peak hours

Frequently Asked Questions

How much does a production Kubernetes cluster on Hetzner cost?

A typical production cluster with 3 control planes (cx33 — €8.49/mo each), 3 workers (cx43 — €15.99/mo each), and 2 HAProxy load balancers (cx23 — €5.49/mo each) costs approximately €84/month on Hetzner Cloud — significantly cheaper than AWS EKS or GKE for equivalent specs.

Should I use ARM (cax) or x86 (cpx/cx) servers for Kubernetes?

At current Hetzner pricing, ARM (cax) servers actually cost 10–30% more per core than the equivalent shared x86 (cx) tier — check the live prices before assuming ARM is cheaper. ARM is fully supported by Kubernetes and can still be worth it for better performance-per-core on multi-arch workloads. Use x86 if you have workloads with x86-only container images or dependencies. Most modern images are multi-arch.

How many control plane nodes do I need for HA?

3 control plane nodes is the standard for production HA. etcd requires an odd number of members for quorum (3 tolerates 1 failure, 5 tolerates 2 failures). Never use 2 or 4.

Do I need dedicated load balancer nodes?

For production, yes. Dedicated HAProxy VMs with Keepalived provide a stable Floating IP for the K8s API and Ingress, surviving control plane restarts. For dev clusters, you can skip this and use a single control plane with NodePort.

Related Tools

Related Guides