Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I was curious about this:

>"There's plenty more in the document, like news that Google's public cloud runs virtual machines in a custom version of the KVM hypervisor."

Does anyone know if this "container inside kvm" is true of their internal infrastructure as well or its just an extra layer of security for their public facing cloud?



Internal Google stuff does not use KVM and that's one reason it took them a while to offer VMs — they had little experience with it.


Do you or anyone else know if there is another reason for doing this besides security?


I can't speak for Google, but there are several reasons. Docker and k8s are not multitenant, so if you want to build a public k8s cloud you need a tenant layer under it. That layer could also be containers (e.g. LXD), but then you're talking about secure nested containers which was not really available in November 2014.


Oh good insight. That makes a lot of sense. Thanks.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: