Index

Module 02 · DevOpsKubernetes

Self-Healing & Autoscaling

Self-Healing and Autoscaling
Self-Healing and Autoscaling · Open board

The harbour master’s foreman watching the crew: who’s actually working, who needs swapping out, and when to call in more hands.

Before you start. From One Crate to a Fleet (why Kubernetes) gave you the loop that keeps checking what’s running against what you asked for and fixes the gap; The Harbor Master (pods, deployments, services) gave you the objects it watches - Pods, the crates it keeps at a fixed count. Kubernetes is the harbour master from The Harbor Master (pods, deployments, services): the program that keeps a fleet of machines running the containers you asked for, and keeps checking. This lesson is what that loop has to do once a headcount stops being enough of an answer: ask whether each crate is actually fit for work, and how many you even need right now.

Continue reading with a plan

The first three lessons of every track are free. This lesson is included with a plan, which unlocks every lesson, board, video, lab and paper for one price.

View plans →Already a member? Sign in

Lab

Your traffic goes up eightfold in three minutes and the HPA is working perfectly. Who still gets an error?

Drag How long a new pod takes to serve to its longest, stay on Follow every reading, and watch Who got an error.

Open The autoscaler lag →

Review DevOps →

Saved in this browser, and to your account when you sign in.