The Kubernetes Effect
&lt;rant&gt;<p>And yet finding people who can reliably install K8s from scratch, who understand what&#x27;s going on under the hood, remains remarkably close to 0.<p>How many people can, within a few hours, tell you how Kubernetes runs DNS, and how it routes packets between containers by default? How do you run an integrated DNS which uses, say, my_service.service.my_namespace instead of my_service.my_namespace?<p>I&#x27;ve found that most installs of k8s have been made using defaults, using tooling that Google has provided. We hired one such administrator, but when asked anything outside of how to run kubectl, they just shrugged and said &quot;it never came up&quot;.<p>The codebase is vast, complicated, and there are few experts who live outside of Google. And it&#x27;s getting more vast, more complicated on a quarterly basis.<p>It bothers me how far operations has gone from &quot;providing reliable systems on which we run software&quot; to &quot;offload work onto the developer at any cost&quot;.<p>&lt;&#x2F;rant&gt;<p>I realize that a lot of this is because of scarcity. The good devops folks (i.e. those who are both competent generalist sysadmins and competent generalist programmers) are few and expensive. That makes pre-packaged &quot;full stack&quot; solutions like GAE, Kubernetes, and Fargate very appealing to leadership.<p>&quot;You don&#x27;t need an operations department to act as a huge drain on your revenue, just re-use your developers&quot; holds a lot of appeal for those high up in the food chain. It&#x27;s even initially appealing to developers! But in the end, it makes as much sense as re-using your developers to do customer service.