This document lists the system limits that apply to Google Distributed Cloud (GDC) air-gapped. System limits are fixed values that cannot be changed.
System limits are applicable to all audience groups, and must be understood by each operator, platform administrator, and application developer to successfully use GDC. For more information, see Audiences for GDC air-gapped documentation .
System limits
The following tables list the system limits that apply to components of GDC, and the value for each system limit.
Cluster management
| System limit | Value | Notes |
|---|---|---|
|
Maximum number of pods in a node
|
110 | The current allocation of pods is based on IP address considerations for any given node. |
|
Maximum number of nodes in a Kubernetes cluster
|
50 | The recommended node limit is 20 nodes for maintainability consideration. The maximum verified number of nodes in a cluster is 50. The maximum number of pods in a cluster is a factor of \( 110 \times \text{number of nodes} \). |
|
Minimum number of worker nodes in a Kubernetes cluster
|
3 | If you create the minimum of three worker nodes in your Kubernetes cluster, you must allocate the machine type for the worker nodes as n2-standard-8
or use GPU machines. |
|
Maximum number of standard clusters
|
Organization and project limited | The maximum number of standard clusters depends on the upper limit of the organization and the available vCPU and IP addresses. Any restrictions placed on a project by a platform administrator might further restrict the number of standard clusters you can create. |
|
Maximum number of shared clusters
|
Organization limited | The maximum number of shared clusters depends on the upper limit of the organization and the available vCPU and IP addresses. |
|
Maximum cluster name size
|
50 characters |
Database
| System limit | Value | Notes |
|---|---|---|
|
Maximum number of single-zone database clusters per organization
|
153 | |
|
Maximum number of Postgres connections per database cluster
|
6000 | The number of maximum connections is highly dependent on workload, database CPU, and memory. When using up to 6000 connections, we recommend 64 vCPU and 1 TB of RAM, though lower CPU and RAM settings might work depending on the workload. |
|
Maximum storage size per database
|
2 TB |
Managed Harbor Service
| System limit | Value | Notes |
|---|---|---|
|
Maximum Harbor registry instances per organization
|
5 | |
|
Maximum Harbor registry instances per GDC project
|
1 | A GDC project is limited to a single Harbor instance, and multiple GDC projects can share a single Harbor instance |
|
Maximum Harbor registry image layer size
|
128 GB | |
|
Maximum Harbor registry storage size
|
1 TB | This storage limit might vary depending on the total storage available in object storage. |
|
Maximum concurrent requests
|
30 | The artifact sizes vary from 1 KB to 1 GB. |
Monitoring
| System limit | Value | Notes |
|---|---|---|
|
Maximum labels per metric
|
40 | |
|
Maximum active time series per metric
|
50,000 | Active time series refers to a unique metric label name/value combination that has recently received new data (samples). |
|
Maximum label value size
|
2048 bytes | |
|
Maximum label name size
|
1024 bytes | |
|
Maximum query range
|
30 days | Restricts a single query from spanning more than 30 days of data. |
|
Maximum query period lookback
|
90 days | Restricts queries to data within the last 90 days (start time must be greater than or equal to now-90 days). |
|
Maximum time series fetched per query
|
100,000 | Queries that attempt to fetch more than 100,000 distinct time series are not allowed. |
|
Maximum samples per query
|
50,000,000 | Limits the total number of samples loaded into memory for a query. |
Multi-zone
| System limit | Value | Notes |
|---|---|---|
|
Maximum number of zones per universe
|
6 | |
|
Maximum number of zones per region
|
6 |
Resource Manager
| System limit | Value | Notes |
|---|---|---|
|
Maximum project name size
|
30 characters | A minimum of four characters must be used for the project name. A project name can contain letters, numbers, single quotes, hyphens, spaces, or exclamation points. For more information, see Project identifiers . |
|
Maximum project ID size
|
30 characters | A minimum of six characters must be used for the project ID. A project ID can contain lowercase letters, numbers, and hyphens. For more information, see Project identifiers . |
|
Maximum number of organizations per zone
|
10 | |
|
Maximum number of projects per organization
|
100 | |
|
Minimum physical servers per customer organization per zone
|
6 physical servers | The physical server number contains three control plane servers and three worker servers. |
