↓ Skip to main content

“A big key to this has been carving out a small chunk of Kubernetes’ features and pretending the rest don’t exist.”

Paul Butlerpaulbutler.org ↗

Jamsocket’s rules for living with Kubernetes are mostly a list of what to avoid: Helm, operators, hand-written YAML, ingress and anything with “mesh” in the name. Google runs the cluster, and the data lives outside it. The interactive workloads that are the actual product run on their own Rust orchestrator, because Kubernetes is the wrong choice whenever a human waits for a pod. The best Kubernetes advice is to use as little of it as possible.