Sheet ⁨03⁩ · ⁨Case studies⁩Surveyed ⁨2026⁩

#Kubernetes

From Blue-Green to Progressive Delivery with Argo Rollouts

From Blue-Green to Progressive Delivery with Argo Rollouts

The incident that started this was not caused by carelessness. It was caused by someone being careful. A release went out at 14:20 on a Tuesday. Error rate climbed within ninety seconds. The on-call

Secrets Management Migration to Vault Without an Outage

Secrets Management Migration to Vault Without an Outage

This project did not start with a security review. It started with a resignation. A senior engineer gave notice, and someone asked the reasonable question of what they could still log into after thei

A Service Mesh Rollout That Was Worth It

A Service Mesh Rollout That Was Worth It

The request that started this was not "can we have a service mesh". It was an auditor asking how we encrypted traffic between services, and the honest answer being that we mostly did not. Everything i

Hardening a CI/CD Supply Chain to SLSA Level 3

Hardening a CI/CD Supply Chain to SLSA Level 3

The question that started this was from an auditor, and it was a fair one: can you prove that the container running in production is the one your pipeline built from the commit you think it was? We ha

Building an Internal Developer Platform on Backstage and GitOps

Building an Internal Developer Platform on Backstage and GitOps

Product teams were spending more time waiting on the platform team than building features. Spinning up a new service meant opening a ticket and waiting for someone to provision a repo, wire up CI, wri

Migrating a Monolith to Kubernetes Without a Big-Bang Cutover

Migrating a Monolith to Kubernetes Without a Big-Bang Cutover

Almost every failed "let's move off the monolith" project shares one detail: the plan was a big-bang cutover. Rewrite in parallel, pick a weekend, flip the switch, and pray. This is the opposite of th

Cutting a SaaS AWS Bill 41% Without Slowing Delivery

Cutting a SaaS AWS Bill 41% Without Slowing Delivery

A growing SaaS ran on EKS with a full GitOps pipeline, and it was over its AWS budget nearly every month. The reflex from leadership was the usual one: freeze features until the bill comes down. That