3 ms·

How do you patch and update your host machines? You need to roll to a backup host, have it take over as primary, patch and reboot your DB host, and then roll ba

How do you patch and update your host machines? You need to roll to a backup host, have it take over as primary, patch and reboot your DB host, and then roll back. I would much rather have an automated process for doing that. Kubernetes provides a framework for allowing that to happen.

sgarland 2y ago
With the exception of kernel patches (and even then, tools like ksplice exist), you generally do not have to restart the OS to apply patches. If the DB itself is being patched, then yes, you’ll restart the DB process, but it’s also not difficult to automate failover.
zsoltkacsandi 2y ago
I was managing a database cluster that served 30% of the population of my entire country. We rarely needed to restart the hosts or database service (maybe once in every two years), and even if we had the failover process took minutes and it was automated. Without Kubernetes. Nowadays people often think that Kubernetes is the only answer for scalability and automation problems. As the matter of fact we had another product that was running on Kubernetes, they are now migrating off from it, turned out that the old school approach with bare EC2 instances, Ansible, Terraform and Packer is much more reliable, scalable and cost effective than Kubernetes. I have to add that yes, we had to write some custom tools, but it was way less effort than managing a K8S cluster and all the software/operators/controllers that are needed for running your workload on it.
- Haaammaa 2y ago
  [dead]
- movedx 2y ago
  > As the matter of fact we had another product that was running on Kubernetes, they are now migrating off from it, turned out that the old school approach with bare EC2 instances, Ansible, Terraform and Packer is much more reliable, scalable and cost effective than Kubernetes. Absolutely it is. I've found this to be the case across a lot of orgs now.

sgarland 2y ago

With the exception of kernel patches (and even then, tools like ksplice exist), you generally do not have to restart the OS to apply patches. If the DB itself is being patched, then yes, you’ll restart the DB process, but it’s also not difficult to automate failover.

zsoltkacsandi 2y ago

I was managing a database cluster that served 30% of the population of my entire country. We rarely needed to restart the hosts or database service (maybe once in every two years), and even if we had the failover process took minutes and it was automated. Without Kubernetes. Nowadays people often think that Kubernetes is the only answer for scalability and automation problems. As the matter of fact we had another product that was running on Kubernetes, they are now migrating off from it, turned out that the old school approach with bare EC2 instances, Ansible, Terraform and Packer is much more reliable, scalable and cost effective than Kubernetes. I have to add that yes, we had to write some custom tools, but it was way less effort than managing a K8S cluster and all the software/operators/controllers that are needed for running your workload on it.

Haaammaa 2y ago
[dead]
movedx 2y ago
> As the matter of fact we had another product that was running on Kubernetes, they are now migrating off from it, turned out that the old school approach with bare EC2 instances, Ansible, Terraform and Packer is much more reliable, scalable and cost effective than Kubernetes. Absolutely it is. I've found this to be the case across a lot of orgs now.