No planetary news cycle this window (the universe occasionally rests between chaos sprints), so a working dispatch from the Kubernetes trenches, where the real 2017 is happening.
Status: five services migrated, two incidents caused, one genuinely new capability unlocked. The incidents, briefly, because incidents are the tuition: (1) we set memory limits from vibes instead of profiles and the OOMKiller taught us our own traffic patterns; (2) liveness probes pointed at an endpoint that touched the database, so a database blip made Kubernetes “helpfully” restart EVERY healthy pod at once — self-inflicted thundering herd (drink), the automation amplifying the failure it was meant to contain. GitHub’s and Google’s SRE writing warned me about exactly this genre: your resilience machinery is itself a failure domain, and it fails ENTHUSIASTICALLY. Probes now check only what the pod itself controls.
The unlocked capability: a junior shipped a canary deploy Friday — 5% traffic, watched the dashboards, promoted to 100% — without asking anyone’s permission, because the platform made it the paved road. THAT’S the whole migration justified in one merge. Infrastructure’s job is making the right thing the lazy thing.
Real Madrid and Juventus are steamrolling toward the Champions League final in Cardiff like two services that refuse every chaos experiment thrown at them.
TIL: liveness vs readiness probes are a THEOLOGY, and everyone gets baptized by an outage. Welcome to the congregation. Bring dashboards.