#kubernetes
The control plane was flapping because of a spinning disk
Healthy nodes, a quiet network, 300 restarts in three days, and a latency budget measured in milliseconds
Bringing a cluster back after the host rebooted
Every VM came back. The cluster did not. Declarative systems converge on config, and the datapath isn't config.
Byte-identical or bust
"Copy it over and switch the reference" is two steps, and the outage lives in the one nobody checks
Never let the AI print a secret
The most important rule wasn't about what I could change. It was about what I was allowed to display.
The version bump that took down an app (and how it self-healed)
One character of YAML, four pods that never started, and two safety nets I didn't know were holding. Every restart is an audit. Schedule them before they schedule you.
What counts as proof
"Verify your work" isn't an instruction. It's a mood. Here's the version that's an instruction. Verify with a different mechanism than the one that made the claim.
The deploy that merged but never deployed
A green PR, a controller reporting success, and not one line of the new code running