This document lists the quotas and limits that apply to Service Extensions.
Quotas
Google Cloud uses quotas to help ensure fairness and reduce spikes in resource use and availability. A quota restricts how much of a Google Cloud resource your Google Cloud project can use. Quotas apply to a range of resource types, including hardware, software, and network components. For example, quotas can restrict the number of API calls to a service, the number of load balancers used concurrently by your project, or the number of projects that you can create. Quotas protect the community of Google Cloud users by preventing the overloading of services. Quotas also help you to manage your own Google Cloud resources.
The Cloud Quotas system does the following:
- Monitors your consumption of Google Cloud products and services
- Restricts your consumption of those resources
- Provides a means to request changes to the quota value
In most cases, when you attempt to consume more of a resource than its quota allows, the system blocks access to the resource, and the task that you're trying to perform fails.
Quotas generally apply at the Google Cloud project level. Your use of a resource in one project doesn't affect your available quota in another project. Within a Google Cloud project, quotas are shared across all applications and IP addresses.
To increase or decrease most quotas, use the Google Cloud console. For more information, see Request a higher quota.
Quotas for Application Load Balancer extensions
The following quotas apply to Application Load Balancer extensions. They can be increased on request.
| Quotas | Value | |
|---|---|---|
| Maximum number of global route extensions in a project | 100 | |
| Maximum number of global traffic extensions in a project | 100 | |
| Maximum number of route extensions per region in a project | 100 | |
| Maximum number of traffic extensions per region in a project | 100 |
Quotas for plugins
The following quotas apply to plugins. They can be increased on request.
| Quota | Value | |
|---|---|---|
| Maximum number of plugins per project | 5 | |
| Maximum number of versions per project | 50 | |
| Maximum number of Wasm actions per project | 5 |
Limits
There are also limits on Service Extensions resources. These limits are unrelated to the quota system. Limits cannot be changed unless otherwise stated.
Usage limits for Application Load Balancer extensions
Service Extensions enforces the following usage limits for Application Load Balancer extensions:
| Usage limit | Value | |
|---|---|---|
| Maximum number of extension chains per attachment point | 5 | |
| Maximum number of callouts in a traffic callout chain | 3 | |
| Maximum number of callouts in a route callout chain | 1 |
Usage limits for plugins
Service Extensions enforces the following usage limits for plugins:
| Usage limit | Value | |
|---|---|---|
Maximum execution duration per request. The duration is the sum of the durations of all Proxy-Wasm callbacks
associated with the request. Plugins that exceed the limit are terminated,
which causes the associated request to return an HTTP |
1 ms | |
| Maximum size of a compiled plugin and plugin configuration | 2 MiB | |
Maximum memory used by a plugin Plugins that exceed this memory are terminated, which causes the associated
request to return an HTTP |
16 MiB | |
Maximum log content emitted by a plugin per request Logs that exceed this limit are truncated. |
16 KiB |