Paths/DevOps Engineer/Kubernetes / Configuration & Resource Limits
Set Resource Limits on a Deployment
A pod without limits can starve its neighbours or monopolise the node. Declare CPU and memory limits, apply the manifest and check the rollout.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- File ~/k8s/deployment.yaml exists and declares a Deployment○
- The manifest sets CPU and memory limits○
- Deployment default/api runs with 3 replicas○
02Walkthrough
1 of 6 revealed- 01
Create the manifests directory
Every manifest for a service lives in the same folder in the repository.
mkdir ~/k8s - 5 locked · each failed submit reveals one
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — kubernetes 1.30 (kind)
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list