Q: Explain the concept of resource requests vs limits. What happens if you only set limits and not requests?
- Request — the guaranteed amount. Scheduler uses this to decide which node has enough room.
Want to master this scenario in a live sandbox? KodeKloud's CKA & CKAD Hands-On Certification Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "When troubleshooting Kubernetes, I always follow a structured layered model: Pod status -> Events -> Logs -> Network. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."
Initial Diagnostics & Root Cause Analysis
If you only set limits and not requests: Kubernetes sets requests equal to limits. This can make scheduling harder because the scheduler thinks each pod needs the full limit amount even if actual usage is much less.
- Request — the guaranteed amount. Scheduler uses this to decide which node has enough room.
- Limit — the maximum. Container is throttled (CPU) or killed (memory) if it exceeds this.
- Set requests accurately based on average usage.
Remediation & Permanent Safeguards
If you set neither: pod gets BestEffort QoS class — it's the first to be evicted under node memory pressure. Recommended practice:
- Set limits higher to allow burst.
- For CPU: it's okay to have a 5x ratio. For memory: be careful — exceeding limit = OOM kill.
- Request — the guaranteed amount. Scheduler uses this to decide which node has enough room.
- Limit — the maximum. Container is throttled (CPU) or killed (memory) if it exceeds this.
- Set requests accurately based on average usage.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Over-granting cluster-admin permissions to pod ServiceAccounts instead of scoping namespace Roles when configuring Explain concept resource Over-granting cluster-wide permissions violates least-privilege principles and allows compromised pods to escalate privileges across namespaces.
-
Referencing mutable latest container tags across production Kubernetes Deployment specs when configuring Explain concept resource
Deployments referencing
:latestrisk inconsistent versions across replica pods and break deterministic rollback capabilities. - Omitting pod readiness probes, causing traffic to hit uninitialized application containers when configuring Explain concept resource Readiness probes gate traffic delivery; missing probes cause Kubernetes to route user requests to pods before dependencies or caches are loaded.
- Executing diagnostic triage without analyzing chronological cluster events and describe outputs when configuring Explain concept resource Cluster events provide sequential timestamps of scheduler decisions, probe failures, and image pull timeouts essential for rapid root-cause isolation.