Live data from Hacker News

Anatomy of My Kubernetes Cluster

ttt.io

1–10 of 38 posts

Re: Anatomy of My Kubernetes Cluster

#3
This is neat. I've been doing the same with Pi 1s and 2s for a few years (http://github.com/rcarmo/raspi-cluster) but stopped short of upgrading to 3s and 4s because of heat/power/cost.

I've found that it is possible to run k3s on SD cards quite well if you're patient, but that the Pi 2 master node spent a _lot_ of time just doing internal stuff even on an otherwise idle cluster, so I went back to Swarm.

(I also had quite a bit of trouble with setting up a container registry, which was hard and undocumented in the first few releases of k3s. Ingress was also a bit of a pain, it's much easier to get traefik working in Swarm...)

Re: Anatomy of My Kubernetes Cluster

#5
Nicely done. I've been meaning to dive into k8s clusters (with either k3s or kind) -- what is the advantage of building a Pi cluster over something like multiple vagrant nodes? Not criticizing at all, just trying to understand.

Re: Anatomy of My Kubernetes Cluster

#6
post #5

Nicely done. I've been meaning to dive into k8s clusters (with either k3s or kind) -- what is the advantage of building a Pi cluster over something like multiple vagrant nodes? Not criticizing at all, just trying to understand.

Not the OP (see my other comment). For me it was the cheap hardware and the fun aspects of the project. It's a tangible thing.

But I also like ARM chips and do occasional embedded development, so I had other motives :)

Re: Anatomy of My Kubernetes Cluster

#9
Why tho? Why not just launch N KVM virtual machines on your linux box? This literally takes minutes, unlike this project which probably took days. And it's much faster once you get it up and running.
Post reply on HN