Kubernetes on Bare Metal

#1

Post by namidark » Wed, Oct 03, 2018, 12:54 PM UTC

Re: Kubernetes on Bare Metal

#2

Post by kalamania » Wed, Oct 03, 2018, 1:19 PM UTC

Interesting, I always thought Bare Metal is synonym for actual hardware server, but the author mixes those:

> Bare metal for this conversation means a regular VM/VPS provider or a regular private provider like Proxmox with no special services - or actual hardware.

Is this a common theme nowadays?

The article itself is of course really nice, it shows that "Kubernetes is hard to set up" theme is not always right.

Re: Kubernetes on Bare Metal

#3

Post by chefgoldbluum » Wed, Oct 03, 2018, 1:31 PM UTC

kalamania wrote: post #2

Interesting, I always thought Bare Metal is synonym for actual hardware server, but the author mixes those: > Bare metal for this conversation means a regular VM/VPS provider or a regular private provider like Proxmox with no special services - or actual hardware. Is this a common theme nowadays? The article itself is of course really nice, it shows that "Kubernetes is hard to set up" theme is not always right.

I thought Bare Metal meant dedicated hardware in the cloud. E.g. Vultr (https://www.vultr.com/pricing/baremetal/) distinguishes VPS vs bare metal as you getting access to entire physical servers without neighbours. Not entirely sure if this is standard nomenclature though.

Re: Kubernetes on Bare Metal

#4

Post by pknopf » Wed, Oct 03, 2018, 1:31 PM UTC

kalamania wrote: post #2

Interesting, I always thought Bare Metal is synonym for actual hardware server, but the author mixes those: > Bare metal for this conversation means a regular VM/VPS provider or a regular private provider like Proxmox with no special services - or actual hardware. Is this a common theme nowadays? The article itself is of course really nice, it shows that "Kubernetes is hard to set up" theme is not always right.

I think he means "native", as in native to the host (regardless if it's virtualized or not).

Re: Kubernetes on Bare Metal

#5

Post by detaro » Wed, Oct 03, 2018, 1:33 PM UTC

kalamania wrote: post #2

Interesting, I always thought Bare Metal is synonym for actual hardware server, but the author mixes those: > Bare metal for this conversation means a regular VM/VPS provider or a regular private provider like Proxmox with no special services - or actual hardware. Is this a common theme nowadays? The article itself is of course really nice, it shows that "Kubernetes is hard to set up" theme is not always right.

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

Re: Kubernetes on Bare Metal

#6

Post by chefgoldbluum » Wed, Oct 03, 2018, 1:34 PM UTC

I used Kubespray on Container Linux with Calico. Maybe I got lucky but I had it working perfectly almost first try. I think I needed to handle like one error in the entire Ansible playbook.

Re: Kubernetes on Bare Metal

#7

Post by jdwithit » Wed, Oct 03, 2018, 1:39 PM UTC

kalamania wrote: post #2

Interesting, I always thought Bare Metal is synonym for actual hardware server, but the author mixes those: > Bare metal for this conversation means a regular VM/VPS provider or a regular private provider like Proxmox with no special services - or actual hardware. Is this a common theme nowadays? The article itself is of course really nice, it shows that "Kubernetes is hard to set up" theme is not always right.

I agree with you. Bare metal to me always implies, well, actual physical servers made out of metal :) A better title might have been "Kubernetes Without a Cloud" or "Kubernetes on-premise". Since what the author is trying to recreate is all the ancillary services that are there for the taking when you run in a cloud provider. Load balancing, storage, cert management, firewall rules, all fronted by easy to consume API's. Which are the actual hard part of setting up a functional k8s cluster.

Re: Kubernetes on Bare Metal

#8

Post by bryanlarsen » Wed, Oct 03, 2018, 1:42 PM UTC

kalamania wrote: post #2

Interesting, I always thought Bare Metal is synonym for actual hardware server, but the author mixes those: > Bare metal for this conversation means a regular VM/VPS provider or a regular private provider like Proxmox with no special services - or actual hardware. Is this a common theme nowadays? The article itself is of course really nice, it shows that "Kubernetes is hard to set up" theme is not always right.

Bare metal is a valid title for this article because his instructions wouldn't change if it actually was bare metal.

Re: Kubernetes on Bare Metal

#9

Post by bryanlarsen » Wed, Oct 03, 2018, 1:43 PM UTC

chefgoldbluum wrote: post #6

I used Kubespray on Container Linux with Calico. Maybe I got lucky but I had it working perfectly almost first try. I think I needed to handle like one error in the entire Ansible playbook.

Agreed, I've set up about 6 different clusters using kubespray and never had any issues. Kubeadm is nice for dev clusters but there are still a bunch of hoops you have to jump through to set up an HA cluster using kubeadm.

Re: Kubernetes on Bare Metal

#10

Post by fooblat » Wed, Oct 03, 2018, 1:57 PM UTC

bryanlarsen wrote: post #8

kalamania wrote: post #2

Interesting, I always thought Bare Metal is synonym for actual hardware server, but the author mixes those: > Bare metal for this conversation means a regular VM/VPS provider or a regular private provider like Proxmox with no special services - or actual hardware. Is this a common theme nowadays? The article itself is of course really nice, it shows that "Kubernetes is hard to set up" theme is not always right.

Bare metal is a valid title for this article because his instructions wouldn't change if it actually was bare metal.

I don't disagree with your statement but I would have expected an article with "bare metal" in the title to cover some of the unique issues associated with bare metal. Like measuring, planning, and managing capacity.