Why this matters
- This topic directly affects how reliably BookStore reaches production — hpa and resource limits keep bookstore pods scaled and schedulable under load..
- Interviewers connect hands-on commands and manifests to real delivery stories, not buzzwords.
- Later modules assume you can explain both the why and the concrete file or command involved.
- Platform maturity shows up when teams automate this instead of relying on tribal knowledge.
Control plane
API serverkubectl / controllers
etcdCluster state store
SchedulerPod → node placement
Controller managerReconcile loops
Worker node
kubeletPod lifecycle
kube-proxyService networking
Container runtimecontainerd
BookStore podYour workload
Requests and limits
Schedulable and capped: BookStore engineers treat this as part of the standard path from laptop to hpa resource limits readiness. Document decisions in the team runbook so on-call knows which knobs exist.
Key ideas
- Requests and limits — primary idea for hpa-resource-limits
- BookStore context — catalog API, checkout, and inventory services share the same pattern
- Automation — prefer pipeline jobs over manual SSH steps
- Verification — staging must prove the change before prod traffic
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 2 sections
- HPA on CPU
- Production checklist
Test yourself
Answer these before moving on — recall is what makes it stick.