Infra tools should be simple, stable, and well-understood. They should compose well together, so it's easy to swap out any individual part for a better one.
Kubernetes is not any these things:
Kubernetes is a bit like systemd, Container Edition. It takes an everything-and-the-kitchen-sink approach to solving what amounts to pretty simple, independent problems, and in doing so makes the problems seem overwhelmingly complex with hundreds of pages of documentation and (literally) millions of lines of code. It promises to abstract away all the complexity of managing infra, but its promises come up short. When things break—and they will break—you're left digging through millions of lines of code to identify the problem.
Kubernetes has incredible ideas at its core... but its implementation is so needlessly complex that it must be replaced.
Our field can do better.
Over the next several posts, I'll break down each major feature of Kubernetes and show how we can achieve it in 2k simple LOC or less with a series of small tools that work well together.
These are tools I've developed over the past four years of working on, managing, and deploying from 1 to 40 servers as a founder and CTO of a startup. We average 100% uptime and deploy 5-10 times per day with a team of just four engineers. Our team's experience ranges from "fresh out of college" to "sysadmin'd thousands of servers for a living." These tools work for all of us.
The tools laid out here should scale well from one to about about a hundred servers and with some minor tweaks could be adapted to scale much larger.
If you adopt this toolset (or way of thinking), you'll get:
And all of this with tools that any one person can read, understand, and debug quickly and fully. If you don't like one of the tools, that's OK! None of these tools are perfect. Swap it out for something else.
That's the whole point.
This will be updated as more parts are released.