Load balancing resource quotas

The following sections describe quotas and limits for load balancers. To change a quota, simply request additional quota using the GCP Console. Limits generally cannot be increased unless specifically noted.

Forwarding Rules

Item Quotas and Limits Notes
Forwarding rules Quota This quota represents the maximum number of forwarding rules in your project, including all load balancing schemes (INTERNAL, INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, and EXTERNAL). This also includes forwarding rules for protocol forwarding and for Classic VPN VPN gateways.
Internal forwarding rules per network See VPC network quotas Contact your GCP sales team if you need to increase this limit.
Internal forwarding rules per peering group See VPC peering quotas and the VPC peering example Contact your GCP sales team if you need to increase this limit.
Ports per internal forwarding rule 5, as a list or a range
Unlimited with the ALL ports option
This limit cannot be increased.
Internal forwarding rules per internal backend service No separate limit Subject to other quotas and limits, multiple internal forwarding rules can reference the same internal backend service.

Target proxies

Item Quotas and Limits Notes
Target HTTP proxies Quota This quota is per project.
Target HTTPS proxies Quota This quota is per project.
Target SSL proxies Quota This quota is per project.
Target TCP proxies Quota This quota is per project.
SSL policies per target HTTPS or target SSL proxy 1 This limit cannot be increased.
SSL certificates per target HTTPS or target SSL proxy 15 This limit cannot be increased.

SSL certificates

Item Quotas and Limits Notes
SSL certificates Quota This quota is per project.

URL maps

Item Quotas and Limits Notes
URL maps Quota This quota is per project.
Host rules per URL map 50 This limit cannot be increased.
Path matchers per URL map 50 This limit cannot be increased.
Path rules per path matcher 50 This limit cannot be increased.
Route rules per path matcher 50 This limit cannot be increased.
Match rules per route rule 50 This limit cannot be increased.
Backend services or backend buckets per path rule 1 backend service or 1 backend bucket, not both This limit cannot be increased.

Backend buckets

Item Quotas and Limits Notes
Backend buckets Quota This quota is per project.

Backend services

Item Quotas and Limits Notes
Backend services Quota This quota includes all backend services (NTERNAL, INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, and EXTERNAL) in your project.
Backend services per TCP Proxy, SSL Proxy, or internal TCP/UDP load balancer 1 This limit cannot be increased.
Maximum number of VM instances per internal backend service

Maximum number of VM instances in the active pool if you configured failover for an internal backend service
250, regardless of how the VMs are allocated among instance groups This limit cannot be increased.
Internal backend services per internal forwarding rule 1 This limit cannot be increased.
Named ports per external backend service 1 This limit cannot be increased.
Named ports per internal backend service 0 This limit cannot be increased.

Backends

Item Quotas and Limits Notes
Instance groups Quota This quota is per project.
Instance group backends per internal backend service 50 This limit cannot be increased.
Backend VMs for an internal TCP/UDP load balancer can be distributed among up to 50 instance groups if the total number of backend VMs is 250 or fewer.
Instance group backends per external backend service 50 This limit cannot be increased.
NEGs per project 100 Contact your GCP sales team if you need to increase this limit.
NEG backends per external backend service 50 This limit cannot be increased.

Endpoints per NEG

Item Quotas and Limits Notes
Endpoints per NEG 10,000 This limit cannot be increased.

VMs per instance group

Item Quotas and Limits Notes
VMs per regional instance group backend for an external backend service Depends on the number of ports specified in the named port for the instance group. It is the smaller of these two:
A: 2,000
B: VMs * (number of ports in the named port that contains the most port numbers) <= 10,000
Contact your GCP sales team if you need to increase this limit.
VMs per zonal instance group backend for an external backend service Depends on the number of ports specified in the named port for the instance group. It is the smaller of these two:
A: 1,000
B: VMs * (number of ports in the named port that contains the most port numbers) <= 10,000
Contact your GCP sales team if you need to increase this limit.
VMs per instance group when the instance group is a backend for an internal backend service No separate limit Backend VMs for an internal TCP/UDP load balancer can be distributed among up to 50 instance groups if the total number of backend VMs is 250 or fewer.

總覽

Google Cloud Load Balancing基於多種理由,我們會針對資源用量強制設定配額上限。舉例來說,限定配額可預防使用量意外暴增的情況,以保障Google Cloud Platform使用者社群的權益。配額也能確保採用免費方案探索 GCP 的使用者不會超出試用範圍。

所有專案最初的配額均相同,您可以要求額外配額來變更配額數量。某些配額可能會依據您使用產品的狀況而自動增加。

權限

如要檢視配額或要求增加配額,身分與存取權管理成員需要具有下列其中一種角色。

工作 必要角色
查看專案的配額 專案擁有者或編輯者「或」配額檢視者
修改配額,要求額外配額 專案擁有者或編輯者配額管理員或具有 serviceusage.quotas.update 權限的自訂角色

查看配額

在 GCP Console中,前往「Quotas」(配額) 頁面。

透過 gcloud 指令列工具執行下列指令來查看您的配額。使用您自己的專案 ID 替換 [PROJECT_ID]

    gcloud compute project-info describe --project [PROJECT_ID]

如要查看某區域的配額使用量,請執行:

    gcloud compute regions describe example-region

要求額外配額

透過 GCP Console的「Quotas」(配額) 頁面要求額外配額。處理配額要求需要花費 24 至 48 小時。

  1. 前往「配額」頁面。

    前往「Quotas」(配額) 頁面

  2. 在「配額」頁面中,選取您要變更的配額。
  3. 按一下頁面頂端的 [編輯配額] 按鈕。
  4. 輸入您的姓名、電子郵件地址和電話號碼,然後點選 [下一步]
  5. 輸入您的配額要求,然後點選 [下一步]
  6. 提交要求。

資源可用性

如果特定類型的資源可以使用,則每項配額代表您能針對該資源建立的最大數量。請特別留意,配額「並不」保證資源可用性。即使您有可用的配額,如果資源無法提供使用,您也無法建立新的資源。舉例來說,您可能擁有足夠配額,能在 us-central1 地區中建立新的地區性外部 IP 位址,但是如果該地區沒有可用的外部 IP 位址,您就無法建立該資源。區域的資源可用性也會影響您建立新資源的能力。

整個地區的資源皆無法提供使用的狀況很罕見。然而,地區內的資源有時可能會耗盡,不過一般來說並不會對該資源類型的服務水準協議造成影響。詳情參閱與資源相關的服務水準協議 (SLA)。

本頁內容對您是否有任何幫助?請提供意見:

傳送您對下列選項的寶貴意見...

這個網頁
Load Balancing