Requests, limits, and autoscaling
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
size JVM pods and scale them.
Planned topics
- Requests are used for scheduling; limits are enforced ceilings.
- Exceeding the memory limit kills the pod (OOMKilled); set the JVM heap relative to the limit (for example
-XX:MaxRAMPercentage=75); verify flags for your JDK version. - CPU limits can throttle; many teams set CPU requests and fewer limits. Decide deliberately.
- Horizontal Pod Autoscaler (HPA) adds or removes replicas based on CPU, memory, or custom metrics.
- Rolling update settings (
maxSurge,maxUnavailable) control the pace and capacity.
Draft outline details
Demonstration
resources block with requests/limits and an HPA targeting 70% CPU, 3 to 10 replicas.
Check your understanding
What happens when a pod exceeds its memory limit?
Show answer
It is OOMKilled and restarted.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.