Quotas for Managed Kubernetes

How many clusters, node groups, nodes, access entries, add-ons and pod identity associations you can have, and how to raise a quota.

Last updated 18 November 2026View as Markdown
QuotaDescriptionDefaultTrialApplies toAdjustable
ClustersKubernetes clusters, in any state (one being deleted still counts)51OrganizationYes
Node groups per clusterNode groups in one cluster102Per clusterYes
Nodes per clusterThe maxSize of all node groups of one cluster, summed505Per clusterYes
Nodes per node groupThe maxSize one node group may have203Per nodegroupYes
Access entries per clusterAccess entries on one cluster10020Per clusterYes
Pod identity associations per clusterPod identity associations on one cluster1.00050Per clusterYes
Add-ons per clusterAdd-ons installed on one cluster3010Per clusterYes

Generated from the quota descriptors: the numbers are the ones the API enforces.

Nodes are counted by node groups' maxSize, the most a group (or the cluster autoscaler) may grow to, not by the nodes running. A cluster being deleted still counts. A request over a quota is refused with 409 before anything is created; the message starts "Quota exceeded:" and names the quota and its limit. Shrinking maxSize is always allowed, even above a lowered quota. A restored deleted cluster counts again from the restore on.

Raise a quota

Ask for a higher value of an adjustable quota, up to its ceiling:

  1. Open Service quotas in the Deutsche Cloud Console.
  2. On the quota's row, choose Request increase.
  3. In Request a quota increase, for New value, enter the value you need.
  4. For What you need it for, enter the reason, then choose Send request.

This needs quotas:ListServiceQuotas to open Service quotas, and quotas:RequestServiceQuotaIncrease to send the request.

Did this page help you?