I do not want to be overly harsh, but this is just lazy clickbait. Nothing new is said here, just a hipster developer making sweeping generalizations about comp

I do not want to be overly harsh, but this is just lazy clickbait. Nothing new is said here, just a hipster developer making sweeping generalizations about companies he does not work for, and does not know their requirements. Honestly, I do not even agree with his premise that you should start at bare metal with manual deployments. Getting some basic automation set up is STUPID EASY between Travis CI, Jenkins, Google App Engine, etc. I feel that toiling to deploy your services is a massive waste of time. Obviously, the reality of this lands somewhere in the middle. I feel like Kubernetes is the whipping boy for "over-complicated infrastructure" undeservedly. Hosting it yourself I am sure is a bear, but there are a LOT of great hosted solutions available. Google Hosted Kubernetes makes my job easier. I write a few Deployments, Services, and Ingress controllers, set up keel.sh to update my deployments based on docker image uploads, and BOOM: Awesome, absurdly automated infrastructure. Log aggregation? Comes out of the box with Stackdriver logging. Monitoring and alerts? Comes out of the box with Stackdriver monitoring. My developers can edit the Kubernetes resources through the Google Cloud GUI. Deploying to an environment is as simple as pushing a docker image with the correct tag and letting Keel take care of the rest. We have looked at alternatives, including bare metal, MULTIPLE TIMES, but in the end, we keep on deciding that Kubernetes is doing a lot for us and we do not want to stop using it.