Also, running services is hard already. Adding another layer that caused existing assumptions to break (networking, storage, etc) made it even harder.
Bare VMs are crazy fast and running apt install is crazy easy. Not looking back at the moment!
Also, running services is hard already. Adding another layer that caused existing assumptions to break (networking, storage, etc) made it even harder.
Bare VMs are crazy fast and running apt install is crazy easy. Not looking back at the moment!
Storage is ughh.
For storage, why not just mount host dirs into the container for stuff you want to persist? Then you’re no worse off than you were before.
One thing I realised with going bare-VM is that most services today are insanely stable. MySQL almost never crashes, Redis definitely almost never crashes, Rails/Passenger/Nginx never have any issues. The things that do happen is disks filling up, application bugs causing issues, or actual VM downtime, which is rare but happens when you have 30 VMs. With Docker or K8s it added a super complex layer that is in development and has issues.
The 4 months we ran our web servers on K8s, I spent at least 1 month debugging issues that ended at an existing open ticket on Github.
Amount of $$ that was spent on Docker infra to run couple dozen servers at the last place I used to contract for.. oh and more fun when those machines have GPUs on them(a lot more fun) then they decided to support Singularity as well because.. I don’t know.
So you manually create and configure your VMs?
Do you have some kind of HA for your database? If a VM goes offline, how quickly can you replace it?
Maybe you don't need to go back to Docker or Kubernetes, but at least consider using one of the hyperscale cloud providers, with its auto-scaling groups and multiple data centers per region, so you can have a system thatheals itself even while you're asleep or on a plane.
less so if you're limited to airgapped/onprem or there are some other security or regulatory considerations
The load balancers we utilize will do failover between them selfs, and do it really well, as in "you don't notice".
Many seem to underestimate the stability of modern virtualization, the build in redundancies, fail over feature and the capabilities of load balancers.
I would guess that most Kubernetes clusters are built on virtual machines, not physical hardware. Meaning that you just now have layers of redundancy.