What job interviews taught me about Kubernetes.
This article is wrong. I’ll explain why below.
First, Kubernetes really sucks. It’s just terrible, terrible technology. The networking stack is atrocious. The Kubeclowns took something that should be a routing table and an iptables rule someone could actually read and buried it under three layers of abstraction that all lie to you in different, incompatible ways. And the networking stuff in there is just so slow. Of course it is — it was created by programmers who understand networking about as well as a llama grasps astrophysics.
I could easily write a 5,000-word rant about how shitty Kubernetes is, and how poorly-designed, about how it incompetently relocates abstractions to inappropriate places that make anything 1,000 times harder to troubleshoot. YAML is also a horrid config language that is ridiculously ill-suited for this purpose.
There are so very many insane and terrible decisions in the architecture of Kubernetes. It is one of the worst technologies I’ve ever used. It’s designed by idiots and a suitable choice only for doofuses.
Back to the main theme, though. Kubernetes became stylish to use and that explains part of its adoption.
But the main reason the article is wrong and that it doesn’t understand what is happening with all the Kubernetes BS is that it ignores the power shift that occurred over the last decade or so in the IT space. The dominance shifted from sysadmin types to developers. And Kubernetes is very friendly to developers. It allows them to package and ship broken nonsense with very little real testing. Of course, devs love that because who wants to test, amirite?
Also, devs are inherently very attracted to complexity. Kubernetes is exceedingly complex so this causes them to love it. It has endless (and pointless) knobs to turn, sliders to move around, switches to clickity-clack, endless dials to twiddle and tweak. All worthless and counterproductive, but devs absolutely go gaga over crap like that.
As I said, Kubernetes won because developers are now dominant. It allowed them to ignore security, good networking practices, compliance, and push absolute garbage to production “reproducibly1.” It’s trash technology2 that achieved preeminence because it allowed devs to run amok in areas they did not understand and hated to deal with.
And yes, I use Kubernetes every day in production. Not my choice, but I am not just guessing about how much of a crapfest it is. I live it.








