Namespaces
Applied Limits to Namespaces
Resource Quota
kspacr applies Resource Quotas, which act as a control mechanism that restricts the total resource usage per namespace. This quota limits the number of objects that can be created in a namespace based on their type. Additionally, it can also cap the overall amount of computational resources that can be used by resources within that specific namespace.
Need more?
Don't hesitate to get in touch if you encounter any problems with these limits. We're more than willing to talk about your specific needs and explore how we can assist you!
Service Limits
When users create resources (pods, services, etc.) in their namespace, the quota system tracks usage to ensure it does not exceed hard resource limits defined in a ResourceQuota.
| Type | Trial Quota | Regular Quota |
|---|---|---|
| ConfigMaps | 10 | 25 |
| CronJobs | 3 | 2x CPU limit |
| Daemon Sets | 0 | 0 |
| Deployments | 3 | 10 |
| Jobs | 3 | 2x CPU limit |
| PVs | 0 | 0 |
| PVCs | 3 | 10 |
| Pods | 8 | 4x CPU limit |
| ReplicationControllers | 3 | 10 |
| Replica Sets | 3 | 10 |
| Secrets | 10 | 25 |
| Services (ClusterIP) | 3 | 25 |
| Services (LoadBalancer) | 0 | 0 |
| Services (NodePort) | 0 | 0 |
| Stateful Sets | 0 | 0 |
CPU & Memory Limits
The quota is also enabled for compute resources like cpu and memory, meaning users must specify requests or limits for those values; otherwise, the quota system may reject pod creation. kspacr does apply defaults for pods that make no compute resource requirements.
| Type | Trial Quota | Regular Quota |
|---|---|---|
| Limits: CPU | 0.5 | 16 |
| Limits: Memory | 1 | 32 |
| Requests: CPU | 0.5 | 16 |
| Requests: Memory | 1 | 32 |
| Requests: Storage | 3 | 100 |