> An ecosystem most knowledgeable SREs will recommend your team not use unless you are able to do a relatively large amount of due diligence and have dedicated

> An ecosystem most knowledgeable SREs will recommend your team not use unless you are able to do a relatively large amount of due diligence and have dedicated staff who are domain experts for kubernetes Who are those 'knowledgeable SREs' and what are they recommending instead? Docker Swarm? VMs? There is a place for those approaches, but people often underestimate the amount of work that is involved to bring large services into production, work that has been packaged and commoditized by K8s, by domain experts. Moreover, it allows people to speak the same language and easily share their solutions. Actual domain experts are required (today) if you want to bring databases and other stateful workloads to Kubernetes. But stateless? I'll run MicroK8s in a Raspberry Pi if I need to run containers. There is so much stuff that's taken care of by K8s that I can't'see why one wouldn't use it, unless they need to just run a single container somewhere. > and proprietary cloud setups. Proprietary? https://github.com/googleforgames/agones https://github.com/googleforgames/agones You don't have to run it on GKE, you know. You can manage it yourself. Which I'm not sure why you would do, since you are complaining about the lack of domain expertise.