Command Palette

Search for a command to run...

Hectal
Phase 4Intermediate5 of 10 in Kubernetes

Scheduling & Scaling

Tell the scheduler what a pod actually needs, control where it's allowed to run, and let the cluster grow and shrink itself automatically under real load.

Every pod so far has been scheduled with zero guidance about what resources it actually needs, or which nodes it should (or shouldn't) run on. This phase fixes that, then builds up to genuinely automatic scaling — both of your application's own pod count, and of the cluster's own worker nodes.

0/4 · 0%
4 topics ~58 min 11 code blocks & diagrams
Start with the first topic
1
4.1

Requests, Limits & Quality of Service

A resource REQUEST tells the scheduler what a pod needs to be placed at all; a LIMIT caps what it's allowed to use — get this wrong and a pod either can't be scheduled anywhere or gets killed for using too much.

15 min 1 diagram 2 code practice

2
4.2

Affinity, Taints & Tolerations

Affinity rules pull pods toward (or away from) specific nodes or other pods; taints and tolerations do the opposite — repelling pods from a node unless they're specifically permitted to land there.

14 min 1 diagram 2 code practice

3
4.3

Horizontal & Vertical Pod Autoscaling

HPA automatically changes how MANY pods are running based on real load; VPA automatically adjusts how much CPU/memory EACH pod requests — two different axes of the same 'stop guessing, let it adapt' idea.

14 min 2 code practice

4
4.4

Cluster Autoscaler & KEDA

HPA scales your pods, but if the cluster's own nodes are already full, that's not enough — the Cluster Autoscaler adds real new nodes when needed, and KEDA extends HPA to scale on genuinely event-driven signals, including down to zero.

15 min 1 diagram 2 code practice