Comment by honkycat
4 hours ago
Recently my company bought another company, and we kept zero of the original engineers, we just had to run the ghost ship.
We walked in, and it was fine. Because it was all kubernetes and laid out like every other app for the most part.
The kube hate is just sad at this point. You need to know like 15 concepts that are all applied in the same way. It mostly just works.
I ported my company over to k8s to solve a concurrency and scaling issues.
What 15 concepts? You're making me worry that I missed something. It was straight forward: pods, nodes, hw type, lifecycle, deployment. They run almost the same docker as the old ec2s used.
What did I miss? Is there something important I need to read?
It’s the pineapple on pizza of ops, people just like to fit in sometimes.
I’ve been running my own personal k8s cluster on digital ocean for the last 5+ years now and it’s dead simple.
Takes me 30 minutes to create a new namespace a deploy an app, love the bonus of having complete flexibility on my stack too — PVC + SQLite ftw
Ghost ship status is not something most orgs aspire to.
The value built on that stability was probably worth acquiring, and it’s infra will decay.