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

>"I think the CoreOS Container OS will live on inside GCP as the customized container os as the default distro used on GKE (managed Kubernetes)."

I found this interesting. Does anyone have any insights how or why Google ended up choosing CoreoS for their GKE offering?



(Former CoreOS/Red Hat)

I am 99% sure that this offering is only similar in nature, not a fork or using any bits from Container Linux


Historically CoreOS was the first OS you could easily PXE boot and have a working container host without performing installation. This was supported not as a secondary thought, but specifically designed to make scale out easier.

A lot of these concepts and benefits apply when you consider cloud images as opposed to PXE boot images. With CoreOS, there was little difference in configuration with these two patters, if the infrastructure had the same topology you could essentially use the same config (VM or Baremetal).

Google Ventures also invested money in CoreOS at one point.


Thanks for the insight. I was wondering what the two patterns are exactly that you referred to here:

>"With CoreOS, there was little difference in configuration with these two patters, if the infrastructure had the same topology you could essentially use the same config (VM or Baremetal)"

Also are re "cloud images" VMs then, similar to AMIs in AWS?

Cheers


Yeah. I didn't mean to imply Google chose CoreOS to work off of, just that the ideas are there.


They didn't. Google's Container-Optimized OS is based on Chromium OS. It's a similar concept, that's all.

https://cloud.google.com/container-optimized-os/docs/concept...




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

Search: