Earlier quoted context omitted.
Using k8s to deploy is easy, setting up a cluster with the 'new' admin command is also straightforward... Doing maintenance on the cluster isn't. Debugging routing issues with it isn't either, configuring a production worthy routing to begin with isn't easy either. it's only quick if you deploy weave-net and call it a day. I would strongly discourage anyone using k8s in production unless it's hosted or you have a ful…
Very few people who suggest using kubernetes are suggesting using kubespray or kubeadm. 99% of companies will want to just pay for a managed kubernetes cluster which, for all intents and purposes, is basically AWS ECS with more features and less vendor lockin. It should be also known that all "run your code on machines" platforms (like ECS) have similar issues. I remember using ECS pre-fargate and dealing with a lot…
Plus disrupting all the developers.
So far every large scale implementation i have seen has cost the developers a year in productivity.