Yes, ... and? Those are much more "standardized" than whatever else any team cooks up. (And k8s along with Go is steadily improving, so I don't see this as "let's use WordPress because its the platform that has the most answers on StackOverflow".)

And even if k8s puts on too many legacy-ness, there are upcoming slimmer manifestations of the core ideas. (Eg. https://github.com/aurae-runtime/aurae )

It doesn’t matter if it adds unneeded complexity as long as it is standardized?

And now you’re suggesting that people use a “simpler” non “standard” implementation?

You need to solve a bunch of SRE/DevOps problem, fearless deploys, rollbacks, canary rollout, blue/green deployment, HA/LB, backups, dev environments, supporting multiple teams, yadda-yadda.

So of course you can implement a minimal complexity solution or you can use something "off the shelf".

k8s is complexity and some of it is definitely unneeded for your situation, but it's also rather general, flexible, well supported, etc.

> you’re suggesting that people use a “simpler” non “standard” implementation?

What I suggested is that if k8s the project/software gets too big to fail, then folks can switch to an alternative. Luckily the k8s concepts and API is open source, so they can be implemented in other projects, and I gave such an example to illustrate that picking k8s is not an Oracle-like vendor lock-in.