Skip to main content
All of the catalog
Scenario

Day-2 Drill: Node Drain Under Load

Cordon and drain a worker node while go-api serves live traffic. A PodDisruptionBudget keeps a minimum number of replicas available, so the scheduler reschedules pods onto the remaining nodes without dropping requests. The grade is the measured request success rate through the drain.

Operationsk3dkind
Definition on GitHub

What you'll do

  • Protect go-api availability during node maintenance with a PodDisruptionBudget
  • Cordon and drain a worker node while traffic runs and watch pods reschedule
  • Verify the PDB held and the request success rate stayed above the SLO
  • Uncordon the node and confirm the cluster returns to full capacity

Stages

  1. 1baseline

    Scale go-api for HA and apply a PodDisruptionBudget so a drain cannot take all replicas down at once

    go-api-availability-budget

Prerequisites

These are installed into the lab cluster for you — listed so you know what the scenario actually depends on.

ingressmonitoring/metricsgo-api

The incident field notes

One real Kubernetes failure a week — the symptom, the commands that found it, and the fix. Written from actual lab runs, not from memory.

Signups aren't open yet — set NEXT_PUBLIC_NEWSLETTER_ENDPOINT to the Kit form endpoint to switch this on.

You'll get the Kubernetes Incident Response Field Guide, plus occasional emails about new scenarios, posts and paid offerings such as courses and workshops. Unsubscribe any time.