I'll clarify that I'm on board with what you're saying. Definitely if you need N machines to split the traffic load, or an application that will auto-restart un

I'll clarify that I'm on board with what you're saying. Definitely if you need N machines to split the traffic load, or an application that will auto-restart under certain conditions, you ought to just use kubernetes. It's a lot easier than rolling it all yourself. What I was trying to target above was more tooling built atop the tooling -- complex instances "the devops stack", rather than _just_ kubernetes. Take for instance, Dhall[1] -- just look at the kind of places that goes[2]! A person coming from a "run docker-compose" world maybe wasn't ever thinking about log rotation, let alone audits, and maybe they should have been. But after they read a marketing blogpost somewhere that's convinced them it is "modern best practices" to use something like Dhall, as the saying goes... now they have two problems. When the person up above mentioned the devops resume madness, that's what I was thinking of and felt it's worth noting does exist, while agreeing that vanilla k8s can be great. 1 - https://dhall-lang.org/ https://dhall-lang.org/ 2 - (shudder) https://docs.dhall-lang.org/howtos/How-to-translate-recursive-code-to-Dhall.html https://docs.dhall-lang.org/howtos/How-to-translate-recursiv...