Quotas and limits

This page explains the quotas and limits for Google Kubernetes Engine (GKE) clusters, nodes, and GKE API requests.

Limits per project

The limits per GKE project are:

Limits per cluster

The limits per GKE cluster are:

Limits Details
Nodes per cluster
  • 5,000 for GKE versions up to 1.17.
  • 15,000 for GKE versions 1.18 and later.

Note: To run more than 5,000 nodes requires lifting a cluster size quota. Contact support for assistance.
Nodes per node pool zone 1,000
Nodes in a zone
  • No node limitations for container-native load balancing with NEG-based Ingress, which is recommended whenever possible. In GKE versions 1.17 and later, NEG-based Ingress is the default mode.
  • 1,000 if you are using Instance Group-based Ingress.
Pods per node 110
Pods per cluster 150,000
Containers per cluster 300,000

Learn more about relevant limits and quotas in the Guidelines for creating scalable clusters.

Limit for API requests

The rate limit for the Kubernetes Engine API is 10 requests per second.

Additional limits and quotas

In addition to per-cluster and per-project limits, specific GKE features have additional limits. For more information, refer to documentation for the features you use.

You might also encounter Compute Engine resource quotas. Additionally, for projects with default regional Compute Engine CPUs quota, container clusters are limited to three per region.

Resource quotas

Starting August 26, 2019, a set of resource quotas is automatically applied to clusters with ten nodes or fewer and to namespaces on those clusters. These quotas, which cannot be removed, protect the cluster's control plane from instability caused by potential bugs in applications deployed to the cluster.

To examine resource quotas, use the following command:

kubectl get resourcequota gke-resource-quotas -o yaml

To view the gke-resource-quotas object for a given namespace, specify the namespace by adding the --namespace option.