Anatomy of My Kubernetes Cluster
ttt.io
ttt.io
So they don't have to do it at their work.
(Unless they work at a large enough company to justify one.)
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...)
Remind me why we need this technology again?
https://www.ebay.com.au/itm/Switching-Power-Supply-DC-5V-12V...
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.
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.
MeanWell has their RS-75-5, which is 60 Watts. Usually around $20.
https://medium.com/@cfatechblog/bare-metal-k8s-clustering-at...
https://medium.com/@cfatechblog/edge-computing-at-chick-fil-...
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.
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.
But I also like ARM chips and do occasional embedded development, so I had other motives :)
I took my desire to build a Pi cluster as an excuse to upgrade to a bigger, newer Anker charging hub.