Scaling Kubernetes to 2,500 Nodes

Re:Scaling Kubernetes to 2,500 Nodes by bdburns on Thursday January 18, 2018 @02:31PM (#16180494)

VMs in all clouds are always tied to specific machines. If that machine fails unexpectedly then those VMs will restart. If it is a controlled reboot (e.g. host update) then they may not restart...

[ Parent | on HN ]

Re:Scaling Kubernetes to 2,500 Nodes by clhodapp on Thursday January 18, 2018 @02:42PM (#16180610)

On Google's cloud, at least, VMs don't get killed for planned hypervisor downtime, which is a potential differentiator for them. Of course, this should matter a lot less for workloads that have been explicitly designed run on Kubernetes...

[ Parent | on HN ]

Re:Scaling Kubernetes to 2,500 Nodes by brianwawok on Thursday January 18, 2018 @02:50PM (#16180679)

Well, at least in Google Cloud for planned updates you can get your VM host migrated and not lose a Node due to a planned maintenance. I am not aware if Azure supports this, but my guess is they do not.

[ Parent | on HN ]

Re:Scaling Kubernetes to 2,500 Nodes by rarudduck on Thursday January 18, 2018 @11:53PM (#16184220)

They (Azure) do for most operations.

https://docs.microsoft.com/en-us/azure/virtual-machines/wind...

I've found actual reboots to be rare - the exception being the recent Spectre / Meltdown patching.

[ Parent | on HN ]