Otherwise i agree. Having just spent a week on-site at a client, you just notice a lot more problems (or start to understand the details of previously identified problems) that are in your capacity to fix.
I agree with everything you said, but this movement has been going on for a long time but and has been very bad at... hisss.. marketing.
These are complex topics and people don't want to put in the effort to understand them so this needs some top-shelf selling power. And there's no money to be made. Just freedom (as in speech).
Worked at a startup that unfortunately went under, trying to reuse heat generated in datacenters. (saves on electricity spend on airco and saves on having to generate heat elsewhere)
I had this exact same problem with the way i & my team approached our kubernetes clusters. I come from a network management background and in that space we all know of a tool called RANCID. A simple tool that logged into your switches/routers, made a dump & removed counters/oscillating data and stored it into CVS.
This predates infra-as-code.. it took years before someone wrote a clone that used Git instead of CVS
Thanks not only for making this, but also describing your process in a blog.
I use ngx_http_auth_request_module a lot and used haproxy a lot in the past but it's currently too limiting for my usecases - now i know it supports lua we're in a whole different ballgame.
There's some good resources out there, the problem here is that most people simply don't care or don't think it's part of their job to fix these things.