Limits

Cluster resources

Set CPU, memory, and storage limits when creating a cluster. Leave room for rollouts and check usage before increasing limits. Your tenant’s resource pool limits the total you can allocate across clusters and databases.

Access and secrets

• Interactive kubeconfig tokens last 8 hours.
• Automation token lifetime is chosen when you generate the kubeconfig.
• Keep each Kubernetes Secret below 1 MiB.
• A managed secret supports up to 100 cluster/namespace targets.

Databases

Resource per instance	Minimum	Maximum
CPU	250m	8
Memory	512Mi	32Gi
Storage	5Gi	500Gi

Storage can grow but cannot shrink. HA databases use two instances of the selected size. The console shows the PostgreSQL versions available when creating a database. Major version upgrades are unavailable.

Bindings

A binding supports up to 10 namespaces. One database supports 20 namespace entries across its bindings, counting each role’s entry separately. Use application namespaces rather than argocd or names beginning with kube-.

Connections

Memory per instance	Connections per role
512Mi	10
768Mi	16
1Gi	21
1536Mi and above	31

Bindings using the same role share its connection budget. Keep application connection pools within that budget.

Names

Use lowercase database names starting with a letter and ending in a letter or digit. Hyphens are allowed, but -- is not. The maximum length is 56 characters minus your tenant name’s length. PostgreSQL reserved names are unavailable.

Registry

Limit	Value
Registries per tenant	1
Access tokens	50
Token expiry	1–365 days; default 90
Login sessions per member	5, lasting 12 hours each
Cluster connections	1 per cluster
Push namespaces per connection	10
Push namespaces across the registry	20

The console shows your storage limit. When full, pushes stop until you delete images or increase the limit; pulls continue.

For a limit you need help with, contact support.