> it throws out all of the interesting parts of Borg This is not true. It throws out the Google-specific parts of Borg (like integration with Google's service

> it throws out all of the interesting parts of Borg This is not true. It throws out the Google-specific parts of Borg (like integration with Google's service discovery, load balancing, and monitoring systems) and improves a number of things compared to Borg. For a good reference on the evolution of Borg into Kubernetes, I recommend the recent Kubernetes Podcast interview with Brian Grant: https://kubernetespodcast.com/episode/043-borg-omega-kubernetes-beyond/ https://kubernetespodcast.com/episode/043-borg-omega-kuberne... > Google themselves don't use it This is not true, and the reasons why it hasn't replaced Borg are related to the integrations I mentioned above (which will take time to integrate or replace) and the zillions of lines of borg config that have built up over the years, rather than concerns that people outside of Google would have (production-worthiness, reliability, etc.) (Disclaimer: I worked on Borg at Google, and now work on Kubernetes at Google.)