Comment by gampleman
14 hours ago
Hilariously written but also too true.
One start up I worked at we had 2 Kubernetes clusters and a rat's nest of microservices for an internal tool that, had we been actually successful at delivering sufficient value would have been used by at most a 100 employees (and those would unlikely be concurrent). And this was an extremely highly valued company at the time.
Another place I worked at we were paying for 2 dev ops engineers (and those guys don't come cheap) to maintain our deployment cluster for 3 apps which each had a single customer (with a handful of users). This whole operation had like 20 people and an engineering team of 8.
This sounds just about right: I have read that Kubernetes is the greek term for "more containers than customers".
We have the same shit and its super annoying too cause in addition I cant do shit without going through the dev ops team even though were 5 engineers.
What were these dev ops engineers doing all day? Surely you can only polish a cluster so much before it's done and there is nothing left to do?
You should have seen the architecture they came up with... it had ALL the bells and whistles you could possibly imagine and cost an absolute fortune.
Of course they eventually got bored and quit. And then it became really annoying since no one else understood anything about it.
It takes approximately 3 months to get it "just right". Luckily, k8s releases (and CNI and auth sidecars, and...) release every 2.8 months.
I work at a place with 8 k8s clusters. We needed to evolve from generation 2 to generation 3 because of "manageability" or something. Gen 3 needed two clusters instead of one. Now we have 8 * (1 + 2) = 24 clusters.
Happy days.