This document describes the quotas and system limits that apply to the connect gateway. Knowing these quotas and system limits helps you plan your workload traffic, avoid authentication errors, and request quota increases when necessary.
This document is for Admins and architects and Platform admins and operators who manage and administer compute resources across teams. To learn more about common roles and example tasks that we reference in Google Cloud content, see Common Google Kubernetes Engine user roles and tasks.
This document lists the quotas and system limits that apply to fleet management.
- Quotas have default values, but you can typically request adjustments.
- System limits are fixed values that can't be changed.
Quotas and limits for connect gateway
The connect gateway has the following quotas and limits:
- Request limit: the connect gateway limits usage to 2,400 requests per minute per fleet. Google Cloud applies this limit to the fleet host project, regardless of how many projects have clusters registered to the fleet.
- Active streams limit: the connect gateway supports a maximum of 10 active streams per fleet host project.
- Request header size limit: there is an 8 KB limit for the request header size. If you use Google Groups to manage access to the connect gateway, the gateway includes user group information in the request header. If a user is a member of many groups, especially groups with long names, the size of the request header can exceed the 8 KB limit and cause authentication errors. For more information, see the troubleshooting documentation.
There are no limits on the amount of data transferred through the gateway in each request.
To view quota usage and limits for your projects, or request a quota adjustment, see View and manage quotas.