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...)
Ok so it's just the API servers. Not every node which is what it sounded like. Typically you wouldn't run normal workloads on the same host as the API. Although these quick "how I did it" articles have a tendency to skip best practice. Still sounds like something isn't right in your environment. They shouldn't be hammered that hard unless you have a very large cluster.
It's a 5V, 20Amp one (thus 100W). There seem to be several of them on Ebay from various vendors.
Using that would mean the 12V laptop power supply, and buck converter to change the 12V to 5V wouldn't be needed. Would probably bring down the cost a little bit too.
Wow it's really beautiful, looks like a real rack.
I wonder, the wires seems to be very hard to bend. When I built custom PC, there's custom build soft power supply / SATA wires for sale. Maybe there should be similar things for USB or other wires that could be easier to tuck in the case.
Ultimately the question is, "how much of the total cpu/memory is used just running kubernetes?" I know prior to rpi4, clusters like this were basically demo/education/bragging rights projects.
If you're serious about messing around with your own k8s cluster, you're way better off just using virtualization. If you really want to run on your own hardware, grab an old laptop or desktop computer and KVM and have at it.
The Pis are just fun toys for people who enjoy tinkering with hardware. This kind of setup isn't really useful (or even educational in any kind of general way outside of the Pi specific details), but some people enjoy it.
It looks like this is being used more as an educational tool for the authors daughter than it is being used for a production workload.
Kube is basically fancy systemd built to run on multiple machines. If you wanted to you could use this for anything you could use one bigger machine and systemd to do.
I started playing with Elixir on mine, but installing Elixir on ARM is enough of a pain that I opted for a Docker image instead so I only had to build it once.
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.
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.
Just about anything not Kubernetes related. I'm currently building a cat toy which combines object detection and reverse kinematics to play with my cat using a laser pointer when she steps into view of the camera.
Why tho? Why not just use a laser pointer yourself? This literally takes minutes, unlike this project which probably took days. And it's much faster once you get it up and running.
So they don't have to do it at their work.
(Unless they work at a large enough company to justify one.)