Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Converting an old MacBook into an always-on personal Kubernetes cluster

devopsdirective.com

Post reply on HN
Print view View original

81–90 of 126 posts

Re: Converting an old MacBook into an always-on personal Kubernetes cluster

#81

Post by tjr225 »

tra3 wrote: post #75
tjr225 wrote: post #65

Earlier quoted context omitted.

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.

The issue is that the battery never gets a chance to discharge if you’re using it as a server. Unless you’re unplugging it and monitoring the battery life and plugging it back in every day.

Re: Converting an old MacBook into an always-on personal Kubernetes cluster

#82

Post by aliswe »

eeZah7Ux wrote: post #58
ForHackernews wrote: post #26

Earlier quoted context omitted.

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.

Kubernetes is the 2020's equivalent of "nobody gets fired for buying IBM" of 1980s.

Sort of, but that's only considering the worst possible outcome...

Re: Converting an old MacBook into an always-on personal Kubernetes cluster

#83

Post by aliswe »

geerlingguy wrote: post #70
bigj0n wrote: post #51

Earlier quoted context omitted.

Kuburnetes is lightweight, extensible and based on open standards, which is the recipe for a long-term solution in this space. It also has first class support in all of the major cloud providers and has an established tooling ecosystem around it.

I'll agree with everything here besides 'lightweight'.

I also take some exception to that, but to be fair I've hward that it fits into a single, 40MB binary...

Re: Converting an old MacBook into an always-on personal Kubernetes cluster

#85

Post by spalas »

wpietri wrote: post #45

For 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…

Interesting, and I agree that this is not a suitable location for running anything important!

I mostly use it for random experimentation/learning and like not having to think about starting up/shutting down Minikube on my main laptop!

Re: Converting an old MacBook into an always-on personal Kubernetes cluster

#86

Post by zimmertr »

rmdashrfstar wrote: post #29
mosselman wrote: post #23

You could sell the MacBook and build a decent raspberrypi cluster with the money you make on it.

A big problem is local storage provisioner for kubernetes is still not GA. I want to use an SSD attached to one master, and use that as storage for the other RPIs. Doing this is still undocumented/the Wild West.

Have you used OpenEBS?

Re: Converting an old MacBook into an always-on personal Kubernetes cluster

#87

Post by zimmertr »

escardin wrote: post #68
vetinari wrote: post #53

Earlier quoted context omitted.

Disclaimer: k8s beginner here. As far as I understand, local storage provisioner is for the node local storage; the storage doesn't follow the workload to whatever node is the pod scheduled, but schedules the pod to the node containing the storage device. It doesn't allow for pods to access local storage outside the node. So for worker nodes using storage on the master node, isn't it better to use either iSCSI or NFS…

This is exactly right. Local storage is conceptually the persistent volume equivalent to an emptydir volume mount. If you want to have a 'storage node' in a simple way, the NFS storage provider is the way to go. You install the nfs client libs on each node, setup an NFS share and configure and run the provisioner[1]. My experience with iSCSI is to stay the heck away from it. It is not what you want. iSCSI is really m…

NFS-Provisioner and NFS-Client have been around for a while. They're about to be promoted from Incubator actually.

Re: Converting an old MacBook into an always-on personal Kubernetes cluster

#89

Post by zimmertr »

mosselman wrote: post #34
rmdashrfstar wrote: post #29

Earlier quoted context omitted.

A big problem is local storage provisioner for kubernetes is still not GA. I want to use an SSD attached to one master, and use that as storage for the other RPIs. Doing this is still undocumented/the Wild West.

I am not a kubernetes expert so I have no idea. Sounds like a fun challenge. I remember seeing something about network mounts for linux in general. Maybe go around kubernetes? If you solve it I'd be interested in how you did it, so an update would be greatly appreciated.

Kubernetes supports pretty much any type of storage through API Extensions so network mounts are supported. People often use the NFS-Client & NFS-Provisioner projects for this.
Post reply on HN