Overview
K8SaaS enforces per-project cluster quotas independent of compute quotas. A cluster quota limits the total number of clusters a project can create. Cluster nodes also consume compute quota (vCPU, RAM, and storage) — both quota systems must have sufficient headroom for cluster creation to succeed. This page covers setting K8SaaS quotas, monitoring usage, and coordinating limits across both services.Prerequisites
- Cloud administrator role
- Project IDs for the projects you wish to quota
Default Quota
By default, K8SaaS applies a platform-wide quota of 20 clusters per project. Projects without an explicit quota record use this default.Set a Project Quota
- Dashboard
- CLI
Navigate to Quotas
Log in to the Xloud Dashboard (
https://connect.<your-domain>) and navigate to
Admin → Containers → Quotas.Create or edit quota
Click Create Quota and fill in:
| Field | Description | Example |
|---|---|---|
| Project | Target project | production-team |
| Hard Limit (Clusters) | Maximum clusters allowed | 10 |
Compute Quota Coordination
K8SaaS cluster nodes consume compute resources. Use the following formula to estimate the compute quota needed for a project’s K8SaaS allocation:Check current project compute quota
Increase compute quota for a project
Monitor Quota Usage
- Dashboard
- CLI
Navigate to Admin → Containers → Quotas to view current usage versus limit
for all projects. Click a project to see individual cluster details.
Update an Existing Quota
Update an existing cluster quota
Next Steps
Monitoring
Monitor cluster health and resource consumption across all projects.
Template Management
Create public templates that standardize cluster resource usage.
Security
Apply RBAC policies to restrict cluster operations per role.
Troubleshooting
Resolve quota-related cluster creation failures.