<story><title>A Manager’s Guide to Kubernetes Adoption</title><url>https://unixism.net/2019/08/a-managers-guide-to-kubernetes-adoption/</url></story><parent_chain></parent_chain><comment><author>orev</author><text>While I know it’s not the main point of the article, I’m getting really tired of the anti-sysadmin bias in pretty much anything related to devops. It seems to be a favorite trope to paint sysadmins as a dying breed of monkeys who are only capable of keeping pets and doing manual tasks when they get around to lifting their knuckles off the floor. Who do you think is writing the playbooks for ansible? How do you think you can even write those things without first having a deep understanding of how the system works and having a set of procedures around them? Who do you think runs the systems your containers sit on top of?&lt;p&gt;Just because infrastructure as code appears to use the same tools that developers use (text files, git) doesn’t mean developers can do the job. Me having access to a pen and paper doesn’t make me Shakespeare.&lt;p&gt;This is especially harmful in an article that claims to be aimed at management, ostensibly trying to set the future path for organizations.&lt;p&gt;P.S. Otherwise a nice overview of things</text></comment>
<story><title>A Manager’s Guide to Kubernetes Adoption</title><url>https://unixism.net/2019/08/a-managers-guide-to-kubernetes-adoption/</url></story><parent_chain></parent_chain><comment><author>true_tuna</author><text>I think the author missed some  key points:&lt;p&gt;1) It will take you longer than you think 
2) It will be harder than you imagined 
3) It’s harder to find people who know it and non-trivial to get good at it (this should have been closer to the top) your project can be done in six months by five k8s experts but you only found one dude who knows it and he’s more a’ight than pro.&lt;p&gt;It’s probably still worth it, just go in with your eyes open.&lt;p&gt;Be prepared for this unfortunate pattern: “this thing I want just doesn’t work and probably never will.&lt;p&gt;Deploying k8s on a small, self-contained project that you just want to set up and go forever is probably a good place to begin.
If you try to move your whole production workflow in one go...
You’re going to have a bad time.</text></comment>