Re:Kubernetes is a red flag signalling premature optimisation
by movedx on Monday July 04, 2022 @05:18PM
(#31981885)
Oh it's most certainly NOT bad! It's very, very good. But it's not the end of the story. Imagine if you could press a button in a recipe book and a stove, pan, some oil, and some eggs appeared and the eggs started cooking... amazing! But that's not the end of the story. You don't have scrambled egg yet. There's still work to be done and after that, there's yet more work to be done - the washing up being one of them.
It's everything that comes afterwards that gets neglected. Not by everyone, granted, but by most.
Re:Kubernetes is a red flag signalling premature optimisation
by roguas on Wednesday July 06, 2022 @12:46PM
(#32003515)
Its bad because kubernetes has a learning curve + typically you'll need someone to deal with it constantly. If your app is simple, you don't need that - simple docker-compose should suffice.
Re:Kubernetes is a red flag signalling premature optimisation
by jbverschoor on Monday July 04, 2022 @06:00PM
(#31982184)
We had J2EE almost 30 years ago. 1 file which described everything and contained everything
Re:Kubernetes is a red flag signalling premature optimisation
by osigurdson on Monday July 04, 2022 @10:53PM
(#31983812)
According to the following link, that literally sounds nothing like Kubernetes. Perhaps a more appropriate analogy to older tech is something like LSF or Slurm.
Re:Kubernetes is a red flag signalling premature optimisation
by scheme271 on Tuesday July 05, 2022 @03:22AM
(#31985332)
LSF and Slurm is still around and kicking on HPC systems. But they're nothing like kubernetes. Maybe close to k8s batch jobs but that's it.
Re:Kubernetes is a red flag signalling premature optimisation
by osigurdson on Tuesday July 05, 2022 @09:51AM
(#31988184)
Finding machines with available cores and memory to run a workload is the fundamental feature that they share.
Genuine question, why is this bad? Is it because k8s can spin it up but becomes unreliable later? I think the industry wants something like k8s - define a deployment in a file and have that work across cloud providers and even on premise. Why can't we have that? It's just machines on a network after all. Maybe k8s itself is just buggy and unreliable but I'm hopeful that something like it becomes ubiquitous eventually.