Why would one want a 'personal kube cluster'?
For learning purposes, I guess.
Converting an old MacBook into an always-on personal Kubernetes cluster
71–80 of 126 posts
Re: Converting an old MacBook into an always-on personal Kubernetes cluster
#72An HP or Dell USFF PC would be a great alternative. Something like an OptiPlex 7010 or 800 G2. You can pick them up for $50 used, if you need more power you can add as large of an SSD as you want plus 16GB of RAM, they're small and quiet and can run Linux.
Yes but this cost the author $0
Re: Converting an old MacBook into an always-on personal Kubernetes cluster
#73For what it's worth, I built one like this on an old Linux laptop. I then moved my home lighting controller onto it as a test. Some months later my house lights stopped working, and I had to spend a few hours applying snippets semi-randomly from Stack Overflow. It could be the problem was due to expired Kubernetes certificates, or it could be something else. Either way, my conclusion was that Kubernetes is really mea…
I have a strong feeling that the added complexity of Kubernetes does not give most use cases a net payoff for hobbyists. A lot of the quirks and monkey wrenching with both Docker and Kubernetes seems to be like problems that in many cases were solved in traditional _NIX systems decades ago. I'm sure there are benefits of throwing some of that architecture out for some scenarios but people shouldn't treat it as a new…
It's not helpful to say some unspecified thing is better than a concrete thing people use.
What Unix tools are an alternative for Docker? I install an app, I download a VM image, and I have a dynamically sized VM with a nice simple UI to control it. VirtalBox is fine too but more heavyweight for multiple VMs at once, and Docker is where the community and premade VMs images are.
Works on any platform.
k8s is probably overkill if you aren't prototyping a production cluster.
Re: Converting an old MacBook into an always-on personal Kubernetes cluster
#74Am I the only person that gets bugged when people use the word cluster for a single computer?
Re: Converting an old MacBook into an always-on personal Kubernetes cluster
#75Earlier quoted context omitted.
except it may not easily survive a power outage
I believe running a MacBook as an always on server will pretty rapidly destroy the battery anyway.
Macbook appears to be pretty intelligent about it's battery. My 2016 is still over 90% healthy and regularly gets over 5 hours on a single charge (load dependent of course). It's pretty much on 24/7.
Re: Converting an old MacBook into an always-on personal Kubernetes cluster
#76Am I the only person that gets bugged when people use the word cluster for a single computer?
Same with groups, no?
Re: Converting an old MacBook into an always-on personal Kubernetes cluster
#77Earlier quoted context omitted.
> Don't really understand the point in investing time in it, as it feels like one of those things you learn on the job as it comes up I don't need to spend my time developing skills for the job I've already got , I need to develop skills for the next job I'll have > most businesses don't even have a compelling reason to switch from the old 3 tier monolith architecture. ...thus showing I can't rely on my employer to k…
You're betting on the technology demand to move to certain direction. To me it feels like investing in stocks, but instead of betting with your money you are betting with your time and brain cycles invested. What makes you so confident that this piece of technology will flourish compared to so many others?
Not the best analogy, IMHO
If the price of a stock or house or investment have been rising for two years, it's risen in cost to get into, and you might never see the gains people have seen in the past; I doubt you'll ever get a bitcoin for a dollar again!
But if job adverts for a new tech have been rising for two years, it doesn't cost any more to learn than on the day it was released. Maybe less, in fact, as there will be more tutorials and more experts to learn from.
Re: Converting an old MacBook into an always-on personal Kubernetes cluster
#78Works just as well on any sufficiently powerful old laptop. I find that any damaged laptop or one with a battery that doesn't hold a charge converts nicely into a home or lab server.
Re: Converting an old MacBook into an always-on personal Kubernetes cluster
#79Earlier quoted context omitted.
Probably for convenience and stability. Linux on the desktop (or on a laptop) has its share of bugs and odd behavior still in 2020.
Definitely no more bugs than its contemporaries. But MacOS does handle low memory conditions much better than Windows does. MacOS (on apple hardware) does have the benefit of optimised fan curves and undervolted CPU profiles which would be hard to replicate in Linux though.
> But MacOS does handle low memory conditions much better than Windows does.
Interesting, my work machine runs a linux vm on a windows 10 host. It regularly uses 95 to 96% of my 16GB RAM. When this happens Linux grinds to a halt yet Programs running on Windows are still usable. MacOS must be amazing,
Re: Converting an old MacBook into an always-on personal Kubernetes cluster
#80Earlier quoted context omitted.
One benefit is to learn how to admin a Kubernetes cluster. Kubernetes knowledge is becoming an important job skill, and if your current employer does not use Kubernetes, you'll need to learn it on your own. > Which IMO, most businesses don't even have a compelling reason to switch from the old 3 tier monolith architecture. Compelling reasons include self-healing, autoscaling, and official support from all major cloud…
This sounds a lot like CV-driven development, rather than any actual use cases. That's not to say it's a bad idea for an individual dev, but might not say great things about our industry.
This subthread is about playing with it at home.