# Kubernetes clusters

Source: https://docs.quake.ai/docs/kubernetes/concepts/kubernetes-clusters
Markdown: https://docs.quake.ai/docs/kubernetes/concepts/kubernetes-clusters.md

---

# Kubernetes clusters

A **Kubernetes cluster** is a control plane plus worker nodes that run your container workloads. On Quake AI you provision clusters through the **[Kubernetes](/docs/kubernetes/concepts/kubernetes)** service (OpenStack Magnum) or by running Kubernetes on **[instances](/docs/compute/concepts/instances)** you manage yourself with kubeadm, k3s, or similar.

Managed offerings on AWS (EKS), Azure (AKS), and DigitalOcean (DOKS) hide the control plane. Quake AI exposes cluster templates and Nova-backed nodes; you operate upgrades, etcd backups, and control-plane sizing unless your template encodes those choices.

## Mapping managed Kubernetes names

| Provider | Their product | On Quake AI |
|---|---|---|
| AWS | EKS cluster | Magnum cluster or self-managed K8s on instances |
| Azure | AKS cluster | Magnum cluster or self-managed K8s on instances |
| Google Cloud | GKE cluster | Magnum cluster or self-managed K8s on instances |
| DigitalOcean | DOKS cluster | Magnum cluster or self-managed K8s on instances |
| Hetzner | Hetzner Kubernetes | Magnum cluster or self-managed K8s on instances |

Networking uses Neutron **networks**, **routers**, and **security groups** under the cluster. Kubernetes Services with `type: LoadBalancer` receive public endpoints through the cluster's cloud controller.

## What to read next

- [Kubernetes on Quake AI](/docs/kubernetes/concepts/kubernetes): Magnum, templates, and operational split
- [Create a cluster](/docs/kubernetes/how-to/create-cluster): Console cluster wizard
- [Migrate from EKS](/docs/kubernetes/migration/migrate-from-eks): control plane and node pool cutover patterns