You have some of those floating around who want to retain their little fiefdoms. I'm at the other end of the spectrum because supporting tens of thousands of snowflakes just makes you want to get a blowtorch. As far as I'm concerned for the right workloads kube can't come fast enough.

The only part I object to is when people get mystical and pie eyed about the idea that putting apps, code, what-have-you in the cloud will mystically make it work well and if it fails you just restart the container or pod and all is well. Which is of course absurd. Bad code is bad code, bad queries run poorly no matter the context. You can buy your way out of some performance issues by scaling up, but that only buys you time at best. IMHO there will always be a need for someone to help people understand why things aren't working well and fix it.

Agreed. When people say k8s/docker is complicated, yes it is, but its simpler and more reliable than the shedload of custom build, config & deployment scripts I've seen in past systems.

that's funny. the same "neckbeards" that are "resisting" k8s have seen this scenario play out over an over and over again. It's very rare that someone actually comes up with something completely new. Usually what' new and exciting are refinements of trying the same ideas that were tried in the past (or changes in the "ecosystem" that enable technologies that were previously not feasible). my prediction is that k8s is NOT going to solve world hunger and it will slowly find its way into being a tool in the toolbelt. I am open to being proven wrong.

It wasn't so much "this will solve world hunger" as much as it was "this thing that we built internally at Google ended up working out pretty well, here's a free and improved reimplementation of it that you can use".

I'm a neckbeard, literally, and it's even gray :). I'm not sure the implied age gap proves out... maybe. I mean there are always early, mainstream and late adopters of a thing. I remember teaching C++ back in the 90's and there was always at least one person in the back of the room who at some point would say "I can do all this with structs and pointers!" or something to that effect. But yeah, ultimately if you get to be my age and are still doing engineering in this business then it's either because you're still doing it at the same place or you're not afraid of change.

Fellow grey neckbeard here,

I resisted vm's at first.

I seriously resisted the idea of the cloud.

I resisted Devops and Agile.

I looked curiously at containers as possibly not just a fad having used jails for years.

Now I'm managing a large and growing exponentially K8s platform and having a great time.

Resistance is futile.

Eventually those die anyway as we raise a new generation that primarily uses contains and all that stuff dips into legacy-rewrite-it-all territory.

could not agree more with you.

Although I disagree your post did make me laugh