3 ms·
Thank you, those both seem like convincing evidence that, at minimum, it's not quite as bleak as I had believed.
by jholman 11y ago
Thank you, those both seem like convincing evidence that, at minimum, it's not quite as bleak as I had believed.
- TheDong 11y agoNote, however, that kubernetes is not used within Google (rather, they use a C++ alternative). Part of why kubernetes uses Go is that it's in a docker-centric container ecosystem. Docker picked Go for its own reasons, not because of Google, so in a way, Kubernetes is picking Go because of the outside community, not because of Google or the language itself.
- jzelinskie 11y agoGCE operates GKE which is a hosted Kubernetes as a service. I'm not saying that Google is using Kubernetes instead of Borg, but that doesn't mean they don't use Kubernetes at all.
- nickpsecurity 11y agoTheParent's explanation makes more sense. Note that the key use case they mentioned for that was an offering for the Docker ecosystem: http://www.infoq.com/news/2014/11/google-cloud-container-engine http://www.infoq.com/news/2014/11/google-cloud-container-eng... So, people are using Kubernetes in the Docker community. Google offers a GCE service for that. This seems incidental to Go with community and demand really driving its use. That they avoid it internally where possible is still a strong point given the large ecosystem developing around Go. Assuming it's true that they avoid it for C++ and Java of course.
- bogomipz 11y agoOh I was just commenting similar to this above. Is the C++ alternative Borg? I believe this spins up a VM like KVM and the runs the container inside the VM.