配额用于指定您可以使用的可计数共享资源的数量。配额由 Google Kubernetes Engine 等 Google Cloud 服务定义。
系统限制是无法更改的固定值。
Google Cloud 使用配额来帮助确保公平性并减少资源使用和可用性的激增。配额用于限制您的 Google Cloud 项目可使用的Google Cloud 资源的数量。配额适用于一系列资源类型，包括硬件、软件和网络组件。例如，配额可以限制对某项服务的 API 调用次数、您的项目并发使用的负载均衡器数量或者您可以创建的项目数量。配额可以防止服务过载，从而保护Google Cloud 用户社区。配额还可以帮助您管理自己的 Google Cloud 资源。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-07-14。"],[],[],null,["# Quotas and limits\n\n*** ** * ** ***\n\nThis document lists the quotas and system limits that apply to\nGoogle Kubernetes Engine.\n\n- *Quotas* specify the amount of a countable, shared resource that you can use. Quotas are defined by Google Cloud services such as Google Kubernetes Engine.\n- *System limits* are fixed values that cannot be changed.\n\nGoogle Cloud uses quotas to help ensure fairness and reduce\nspikes in resource use and availability. A quota restricts how much of a\nGoogle Cloud resource your Google Cloud project can use. Quotas\napply to a range of resource types, including hardware, software, and network\ncomponents. For example, quotas can restrict the number of API calls to a\nservice, the number of load balancers used concurrently by your project, or the\nnumber of projects that you can create. Quotas protect the community of\nGoogle Cloud users by preventing the overloading of services. Quotas also\nhelp you to manage your own Google Cloud resources.\n\nThe Cloud Quotas system does the following:\n\n- Monitors your consumption of Google Cloud products and services\n- Restricts your consumption of those resources\n- Provides a way to [request changes to the quota value](/docs/quotas/help/request_increase) and [automate quota adjustments](/docs/quotas/quota-adjuster)\n\nIn most cases, when you attempt to consume more of a resource than its quota\nallows, the system blocks access to the resource, and the task that\nyou're trying to perform fails.\n\nQuotas generally apply at the Google Cloud project\nlevel. Your use of a resource in one project doesn't affect\nyour available quota in another project. Within a Google Cloud project, quotas\nare shared across all applications and IP addresses.\n\nTo adjust most quotas, use the Google Cloud console.\nFor more information, see\n[Request a quota adjustment](/docs/quotas/help/request_increase).\n\n\nThere are also *system limits* on GKE resources.\nSystem limits can't be changed.\n\nQuotas per project\n------------------\n\nGKE has the following quotas:\n\n- [Zonal clusters](/kubernetes-engine/docs/concepts/types-of-clusters#zonal_clusters) per zone\n- [Regional clusters](/kubernetes-engine/docs/concepts/types-of-clusters#regional_clusters) per region\n- API reads\n- API writes\n\n**Note** : Clusters created in the [Autopilot mode](/kubernetes-engine/docs/concepts/types-of-clusters#modes)\nare pre-configured as regional clusters.\n\n### Check your quota\n\nQuotas can be view in Google Cloud console, go to the **Quotas** page.\n\n[Go to Quotas](https://console.cloud.google.com/iam-admin/quotas)\n\nTo managing and request for additional quotas, see [view and manage quotas](/kubernetes-engine/quotas/view-manage)\n\nLimits per cluster\n------------------\n\nThe following tables describe the limits per GKE cluster.\n\nAny GKE versions specified in the following table apply to both\ncluster nodes and the control plane.\n\nAs a platform administrator, we recommend you to get familiar with how quotas affect large workloads that run on GKE. For additional recommendations, best practices, limits, and quotas for large workloads, see [Guidelines for creating scalable clusters](/kubernetes-engine/docs/best-practices/scalability).\n\nResource quotas\n---------------\n\n| **Note:** GKE doesn't enforce the following Kubernetes resource quotas for clusters running version 1.28 or later, however GKE doesn't restrict you from applying your own Kubernetes resource quotas.\n\nFor clusters with under 100 nodes, GKE applies\n[Kubernetes resource quota](https://kubernetes.io/docs/concepts/policy/resource-quotas/) to every namespace. These quotas protect the cluster's control\nplane from instability caused by potential bugs in applications deployed to the\ncluster. You cannot remove these quotas because they are enforced by\nGKE.\n\nGKE automatically updates resource quota values in proportion to\nthe number of nodes. For clusters with over 100 nodes, GKE\nremoves the resource quota.\n\nTo examine resource quotas, use the following command: \n\n kubectl get resourcequota gke-resource-quotas -o yaml\n\nTo view the values for a given namespace, specify the namespace by adding the\n`--namespace` option.\n\nNotes\n-----\n\n1.\n The maximum number of Pods per GKE Standard cluster includes system Pods.\n The number of system Pods varies depending on cluster configuration and enabled features.\n [↩](#fnref1)\n\n2.\n The maximum number of Pods that can fit in a node depends on\n the size of your Pod resource requests and the capacity of the node. You\n might not reach every limit at the same time. As a best practice, we\n recommend that you load test large deployments.\n [↩](#fnref2)"]]
