Troubleshooting·Kubernetes and Cloud Native Associate
Replica Count and Cluster Capacity
Scale to 8 with a ResourceQuota and an HPA in place and you land on 4. One limiter rejected Pod creation with an explicit quota error; the other quietly rewrote your replica count. Telling them apart is the skill.
Cloud Native Architecture Guide 33 of 46 Intermediate
- Kubernetes1.36.4
- Serverlessnone installed (no KEDA, no Knative)
- TimeAbout 16 min
- Reviewed22 August 2026
Written against the versions above. The objects here are long-stable. Quota and HPA behaviour has not changed materially in years.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| CKA1001 | 192.168.0.175 | Ubuntu 26.04 LTS | Control Plane Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE02 | 192.168.0.177 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
Before you start
- A namespace you can put a quota on, and a Deployment with resource requests.
- The autoscaling guide, since an HPA is one of the two limiters here.
-
Put a quota on the namespace
-
Ask for eight
-
Limiter one: the quota refused, and said so
-
Limiter two: the HPA rewrote your number