What is Managed Kubernetes?

Managed Kubernetes runs the control plane of upstream Kubernetes clusters for you; your nodes are compute instances in your network, and kubectl signs in with your {{product}} identity.

Last updated 18 November 2026View as Markdown

A cluster is upstream Kubernetes 1.36 or 1.37. Deutsche Cloud runs its control plane (API server, etcd, scheduler, controller manager) on machines of its own; you add node groups, which are compute instances in your network that join the cluster as nodes. You find it under Kubernetes in the Deutsche Cloud Console; in the API, IAM and the CLI it is eks.

Managed Kubernetes can be a preview on an installation. Then Deutsche Cloud switches it on per organization: without that, the console shows a preview notice and the /eks/api routes answer 404 (all but the public token-issuer documents that clusters read).

When to use it

  • You want to run containers with Kubernetes and do not want to run etcd, the API server, their certificates, backups and upgrades yourself.
  • You want to see what runs: every provisioning step, upgrade step, repair and access change is written to the cluster's Activity.
  • You want kubectl access without long-lived credentials: tokens last ten minutes and are issued only to people with an access entry.

Concepts

Term Meaning
Cluster A Kubernetes control plane plus its API endpoint. Addressed by id (ewk-…) or by name.
Tier dev: one control-plane machine, no SLA. standard: three control-plane machines, with an SLA.
Node group Compute instances of one server type (or its sold-out fallbacks) that join the cluster as nodes, sized by a minimum, desired and maximum count.
Access entry An IAM user, group or role allowed into the cluster, with the access policies that say what it may do there.
Access policy ClusterAdmin, Admin, Edit or View: the Kubernetes roles cluster-admin, admin, edit and view.
Add-on metrics-server, traefik, cert-manager or external-dns, installed and kept at the version you choose.
Pod identity association Lets the pods of one service account act as an IAM role, with no access key stored in the cluster.
Snapshot A backup of the cluster's etcd (every Kubernetes object), taken by Deutsche Cloud. Volumes are not part of it.
Activity The cluster's event stream: provisioning, changes, upgrades, repairs, access.

More in Clusters and node groups and Cluster access.

Pricing

  • Control plane: a fee per hour by tier while the cluster is active, updating or restoring: standard €0.10, dev €0.02. A cluster that is being created, has failed or is being deleted is not charged. The first 744 dev control-plane hours of each month are free for the organization, shared by all its dev clusters. While Kubernetes is a preview on the installation, the hours are recorded at €0.
  • Nodes are compute instances and bill as compute.
  • Services of type LoadBalancer are load balancers and bill as load balancers.
  • PersistentVolumes are volumes and bill as volumes.
  • Add-ons, access entries and pod identity associations are not charged.

The create form shows an estimate before you create anything.

Regions

Clusters are in Germany (de1, zones de1a Falkenstein and de1b Nuremberg) unless your organization allows EU locations outside Germany; then a cluster can also run in Helsinki, Finland (fi1). A node group has no region of its own: it is in its cluster's.

Interfaces

  • The Deutsche Cloud Console, under Kubernetes.
  • The CLI: dcloud eks …; see the CLI Command Reference. dcloud eks update-kubeconfig adds a cluster to your kubeconfig.
  • The HTTP API under /eks/api; see the API Reference.
  • Terraform: dcloud_eks_cluster, dcloud_eks_nodegroup, dcloud_eks_access_entry, dcloud_eks_access_policy_association, dcloud_eks_addon and dcloud_eks_pod_identity_association.

Next steps

Did this page help you?