A platform/paradigm is a tool for building appliances/answers. Out of the box, there are a bunch of builtin kube applicances/answers: Kubernetes runs processes

A platform/paradigm is a tool for building appliances/answers. Out of the box, there are a bunch of builtin kube applicances/answers: Kubernetes runs processes/containers, network configuration, storage, and load-balancing/ingress. Adding vpn/wireguard, logging, metrics, whatever else have you will follow the same templates & ideas. But I think we're down to counting trees (number of builtin objects/appliances) rather than grokking the forest (that there's a general api-server-aka-state/operator dual concept that works everywhere, with many abundant appliance/use-cases slotting in & operated on the same way) when we myopically focus on individual use cases. And ignore the system. > If you do not have an answer to I think I did! I suggested a general, all-purpose, well known flexible system applicable everywhere. It just didn't click for you. And in counter, please- requesting again- answer what you would suggest in lieu of Kubernetes please. So far you've had only negative, degrading, downputting things to say, and I'd like to see you try to make a positive cases for something, sometime, anytime, so we might have some reasonable comparison to assess & reason over. Alongside your destructive negative criticism, offer some positive examples of what you think does better, offers a clearer example of accomplishment. So we can compare & assess, have a field of play rather than only you taking shots against the champion forever. If you don't have any counter-examples, I'm not sure how we can keep discussing the worth of this system/paradigm!