I got it right too. But for an entirely naive reason. The smaller the components the more complex machines you would need - more expensive. Plus the more wiring on the io 3 vs 3+
The article mentions that by ditching the efficiency cores and lowering the voltage on their new "performance" cores they have achieved the same efficiency. My bachelor is on electronics eng, and my professional career has nothing to do with it. I know there's more to it that that said in the article: Why they've never tried to lower voltage before instead of having efficiency cores? And what do they mean, they lowered voltage, are we talking 5V range to 3V range?
One way of doing things without kube I imagine as follows: I do coding, build an image and push the container to a container repo. Then I have to ssh into the server and stop and start the container with the new version.
Which I find time consuming. How could I automate this deployment cycle? What people usually do?
Sorry, I guess, the title doesn't highlight what I am looking for. I am looking for the easiest way to set up a kubernetes cluster on premise. Is there a solution for it? Without using kubeadm and messing with the network.
Some folks mentioned not messing around with kube on-prem. I agree with that, as long as there is another solution that would allow me to easily deploy apps without touching ubuntu and the apps could be resilient and scalable in future with a click of a button. Are there such non-kube solutions?
Thank you, indeed!
I am trying to avoid self management. Considering the complexity of a manual setup, I am looking for some abstraction; "managed" k8s solutions like mentioned above. I have two choices at the moment either go with more or less managed k8s or go with something similar to Heroku (but OSS) with build pipelines.
I'm sure there are solutions that I might be missing...