I've written (well, participated in development of) two Kubernetes operators, and support about a dozen of them (in our own deployment of Kubernetes): Jupyter,

I've written (well, participated in development of) two Kubernetes operators, and support about a dozen of them (in our own deployment of Kubernetes): Jupyter, PostgreSQL, a bunch of Prometheus operators and a handful of proprietary ones. In my years of working with Kubernetes I cannot shake the feeling that it's, basically, an MLM. It carefully obscures it's functionality by hiding behind opaque definitions. It doesn't really work, when push comes to shove. And, most importantly, it survives in a parasitic kind of way: by piggybacking on those who develop all kinds of extensions, be it operators, custom networking or storage plugins, authentication and so on. My problem is I cannot find who stands at the top of the pyramid. There's Cloudnative Foundation, but all it does is selling certifications nobody really needs... so, that cannot possibly be it. No big name doesn't really benefit from this in an obvious way... So... anyways, when I hear people argue about how to implement this or another extension of Kubernetes, it rings the same as when people argue about styles of agile, or code readability etc. nonsense. There isn't a good way. There is not acceptance criteria. The whole system is flawed to no end.