Kubernetes on Bare Metal • Hacker News Board

Re: Kubernetes on Bare Metal

#31

Post by detaro » Thu, Oct 04, 2018, 11:27 AM UTC

tyingq wrote: post #11

detaro wrote: post #5

Earlier quoted context omitted.

Calling VMs/VPS bare metal is unusual from what I see.

There is a sort of "in between" use of the term for a VPS that doesn't share the underlying real server with any other VPS instances. Like these: https://www.scaleway.com/baremetal-cloud-servers/ That's pushing it a little for me. Certainly calling a regular VPS bare metal is silly.

The page you link claims that there is no hypervisor running, so it's not a VM, but "true" Bare Metal.

Re: Kubernetes on Bare Metal

#32

Post by buttersbrian » Thu, Oct 04, 2018, 2:12 PM UTC

What's the best approach for on-premise k8 clusters?

Re: Kubernetes on Bare Metal

#33

Post by tyingq » Thu, Oct 04, 2018, 2:15 PM UTC

detaro wrote: post #31

tyingq wrote: post #11

Earlier quoted context omitted.

There is a sort of "in between" use of the term for a VPS that doesn't share the underlying real server with any other VPS instances. Like these: https://www.scaleway.com/baremetal-cloud-servers/ That's pushing it a little for me. Certainly calling a regular VPS bare metal is silly.

The page you link claims that there is no hypervisor running, so it's not a VM, but "true" Bare Metal.

I wonder if it's a single container, running your OS on top of theirs then. I don't see how their API would work sans both a VM and containers. Unless maybe they are supplying a fixed set of tweaked distributions.

Re: Kubernetes on Bare Metal

#34

Post by detaro » Thu, Oct 04, 2018, 6:26 PM UTC

tyingq wrote: post #33

detaro wrote: post #31

Earlier quoted context omitted.

The page you link claims that there is no hypervisor running, so it's not a VM, but "true" Bare Metal.

I wonder if it's a single container, running your OS on top of theirs then. I don't see how their API would work sans both a VM and containers. Unless maybe they are supplying a fixed set of tweaked distributions.

I don't know their specific setup, but Bare Metal providers generally either netboot your image, or netboot something that copies your image to local disk, and then reboot into it. That can be automated quite far, the biggest issue is having a hardware platform that can't be permanently compromised by the running OS (e.g. on a typical x86 system, the OS could reflash the BIOS or firmware of other components)