Re:The Evolution of Container Usage at Netflix
by richardwhiuk on Friday April 21, 2017 @07:28AM
(#14164580)
Or use something like GKE where the containers should be running directly on hardware, so you only have one layer.
[ Parent
| on HN ]
Re:The Evolution of Container Usage at Netflix
by nailer on Friday April 21, 2017 @07:33AM
(#14164599)
"Bare-metal" means running directly on hardware. But yes, GKE would also join Triton and Red Shift (provided it has similar container isolation capabilities).
Re:The Evolution of Container Usage at Netflix
by nailer on Friday April 21, 2017 @09:49AM
(#14165565)
Actually, as 0x74696d mentions below, GKE is also not bare metal.
Doing a little research: GKE runs on https://cloud.google.com/container-optimized-os/docs/ which is designed for GCE, which runs on KVM: https://cloud.google.com/compute/docs/faq
So it looks like just Triton and Red Shift.
Disclaimer: I used to work at Red Hat, which means I like the people behind Red Shift, but that also means I hate the people behind Triton as part of the early 2000s Linux/Solaris wars.
Re:The Evolution of Container Usage at Netflix
by 0x74696d on Friday April 21, 2017 @08:37AM
(#14164954)
GKE clusters run on VMs, not on bare metal.
Re:The Evolution of Container Usage at Netflix
by lima on Friday April 21, 2017 @10:37AM
(#14165955)
Containers don't actually run directly on hardware with GCE - there's still a virtualization layer in-between.
I'm 99% sure that Google runs one VM per container because that's the only way to make it safe.
Anything else would be insane.
Re:The Evolution of Container Usage at Netflix
by outworlder on Friday April 21, 2017 @03:14PM
(#14168469)
> I'm 99% sure that Google runs one VM per container
I'm 100% sure you are wrong. You might as well just use VMs.
Containers are not only about safety, you know.
Re:The Evolution of Container Usage at Netflix
by lima on Friday April 21, 2017 @06:40PM
(#14169990)
I stand corrected, it's a bunch of VMs per customer but still no multi-tenancy.