Quotas
This document contains current content limits and request quotas for Cloud Service Mesh.
A quota restricts how much of a shared Google Cloud resource your Google Cloud project can use, including hardware, software, and network components. Therefore, quotas are a part of a system that does the following:
- Monitors your use or consumption of Google Cloud products and services.
- Restricts your consumption of those resources, for reasons that include ensuring fairness and reducing spikes in usage.
- Maintains configurations that automatically enforce prescribed restrictions.
- Provides a means to request or make changes to the quota.
In most cases, when a quota is exceeded, the system immediately blocks access to the relevant Google resource, and the task that you're trying to perform fails. In most cases, quotas apply to each Google Cloud project and are shared across all applications and IP addresses that use that Google Cloud project.
There are also limits on Cloud Service Mesh resources. These limits are unrelated to the quota system. Limits cannot be changed unless otherwise stated.
Note that Istio resources are translated into Cloud Service Mesh resources that count against the quotas that follow.
Limits
Cloud Service Mesh has a limit of 100 queries per second (QPS) per Google Cloud project.
All existing forwarding rule, backend service, and other load-balancing limits and quotas per project apply to Cloud Service Mesh deployments based on Google Cloud load balancing and service routing APIs.
URL map limits
URL maps for Cloud Service Mesh with the load-balancing APIs are subject to the following per-project limits.
Item | Quotas and limits | Notes |
---|---|---|
URL maps | Quota | This quota is per project. |
Paths in path rules | 50 | This limit cannot be increased. |
Match rules in route rules | 50 | This limit cannot be increased. |
Host rules per URL map | 2,500 | This limit cannot be increased. |
Path matchers per URL map | 2,500 | This limit cannot be increased. |
Path rules per path matcher | 500 | This limit cannot be increased. |
Route rules per path matcher | 500 | This limit cannot be increased. |
Header matches per match rule | 50 | This limit cannot be increased. |
Query parameter matches per match rule | 50 | This limit cannot be increased. |
Metadata filters per match rule | 5 | This limit cannot be increased. |
Filter labels per metadata filter | 64 | This limit cannot be increased. |
Hosts per host rule | 100 | This limit cannot be increased. |
Tests per URL map | 100 | This limit cannot be increased. |
Size of URL maps | 524 KB | This limit cannot be increased. |
Weighted backend services per route action | 10 | This limit cannot be increased. |
If you exceed one of the limits in the table, you see an error such as the following:
Value for field 'resource.hostRules[0].hosts' is too large: maximum size 100 element(s);actual size 107.
Service routing API limits
Item | Notes |
---|---|
Meshes | This quota is per project. |
Gateways | This quota is per project. |
GrpcRoutes | This quota is per project. |
HttpRoutes | This quota is per project. |
TcpRoutes | This quota is per project. |
TlsRoutes | This quota is per project. |
Network security API limits
Item | Quotas and limits | Notes |
---|---|---|
clientTlsPolicy | 500 | This quota is per project. |
serverTlsPolicy | 500 | This quota is per project. |
AuthorizationPolicy | 500 | This quota is per project. |
EndpointPolicy | 750 | This quota is per project. |
Service load balancing policy
Item | Quotas and limits | Notes |
---|---|---|
ServiceLbPolicies | Quota | This quota is per project. |
To increase or decrease most quotas, use the Google Cloud console. For more information, see Request a higher quota.
Manage quotas
Cloud Service Mesh enforces quotas on resource usage for various reasons. For example, quotas protect the community of Google Cloud users by preventing unforeseen spikes in usage. Quotas also help users who are exploring Google Cloud with the free tier to stay within their trial.
All projects start with the same quotas, which you can change by requesting additional quota. Some quotas might increase automatically based on your use of a product.
Permissions
To view quotas or request quota increases, Identity and Access Management (IAM) principals need one of the following roles.
Task | Required role |
---|---|
Check quotas for a project | One of the following:
|
Modify quotas, request additional quota | One of the following:
|
Check your quota
Console
- In the Google Cloud console, go to the Quotas page.
- To search for the quota that you want to update, use the Filter table. If you don't know the name of the quota, use the links on this page instead.
gcloud
Using the Google Cloud CLI, run the following command to
check your quotas. Replace PROJECT_ID
with your own project ID.
gcloud compute project-info describe --project PROJECT_ID
To check your used quota in a region, run the following command:
gcloud compute regions describe example-region
Errors when exceeding your quota
If you exceed a quota with a gcloud
command,
gcloud
outputs a quota exceeded
error
message and returns with the exit code 1
.
If you exceed a quota with an API request, Google Cloud returns the
following HTTP status code: 413 Request Entity Too Large
.
Request additional quota
To increase or decrease most quotas, use the Google Cloud console. For more information, see Request a higher quota.
Console
- In the Google Cloud console, go to the Quotas page.
- On the Quotas page, select the quotas that you want to change.
- At the top of the page, click Edit quotas.
- For Name, enter your name.
- Optional: For Phone, enter a phone number.
- Submit your request. Quota requests take 24 to 48 hours to process.
Resource availability
Each quota represents a maximum number for a particular type of resource that you can create, if that resource is available. It's important to note that quotas don't guarantee resource availability. Even if you have available quota, you can't create a new resource if it is not available.
For example, you might have sufficient quota to create a new regional, external IP address
in the us-central1
region. However, that is not possible if there are no
available external IP addresses in that region. Zonal resource
availability can also affect your ability to create a new resource.
Situations where resources are unavailable in an entire region are rare. However, resources within a zone can be depleted from time to time, typically without impact to the service level agreement (SLA) for the type of resource. For more information, review the relevant SLA for the resource.