k3d for local Kubernetes turned "reset your cluster" from a coffee-break chore into a one-line reflex. Our onboarding doc had a line I grew to hate: "if your local cluster is acting weird, delete it and start over (grab a coffee, this takes a few minutes)." On minikube and Docker Desktop's built-in Kubernetes, that was literally minutes of VM boot and a laptop that sounded like it was preparing for liftoff. Here's the switch, the command, and the gotchas.
What broke
Recreating a cluster was expensive, so people avoided it. They nursed broken clusters with hacks instead of resetting to a known-good state, which manufactured "works on my machine" bugs that cost even more time. Multiply a few resets a day across eight engineers: real hours burned on a thing that should be instant.
I wanted local Kubernetes disposable — cheap enough that recreating it is boring. There's a solid walkthrough of standing up a real local cluster in a couple of minutes at this k3d cluster writeup.
What k3d actually is
