Resource Quotas

Every kubestart cluster enforces resource quotas based on your package. These quotas set hard limits on what your workloads can consume.

Quotas by package

Resource	Small	Medium	Large
CPU	2 cores	6 cores	12 cores
Memory	8 GiB	12 GiB	24 GiB
Storage	40 GiB	120 GiB	320 GiB
Pods	25	100	200
PVCs	4	10	20
LoadBalancer services	0	0	0
NodePort services	0	0	0

Default resource limits

If you create a pod without specifying resources.limits, the platform applies default limits automatically. This prevents a single pod from consuming all available resources.

Package	Default CPU limit	Default memory limit
Small	500m	512 Mi
Medium	750m	768 Mi
Large	1000m	1 Gi

Tip

Always set explicit resources.requests and resources.limits on your workloads. The defaults are conservative — your application may need more or less depending on its requirements.

Checking your usage

Use kubectl to inspect current resource consumption against your quota:

kubectl describe resourcequota

This shows each resource type, how much is currently used, and the hard limit. For example:

Name:           default
Namespace:      default
Resource        Used   Hard
--------        ----   ----
cpu             1500m  2
memory          2Gi    8Gi
pods            5      25

What happens when you hit a quota

When a quota is reached, new pods or PVCs that would exceed the limit are rejected by the API server. Existing workloads continue running normally. You’ll see an error like:

Error from server (Forbidden): exceeded quota: default,
requested: cpu=500m, used: cpu=1800m, limited: cpu=2

To resolve this, either reduce your existing workloads or upgrade to a larger package.

Related

• Storage — volume sizes and deletion protection.
• Bandwidth & Limits — network transfer limits.