Anatomy of My Kubernetes Cluster
1–10 of 38 posts
Re: Anatomy of My Kubernetes Cluster
#2Re: Anatomy of My Kubernetes Cluster
#3I'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
#4Re: Anatomy of My Kubernetes Cluster
#5Re: Anatomy of My Kubernetes Cluster
#6Nicely 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.
But I also like ARM chips and do occasional embedded development, so I had other motives :)
Re: Anatomy of My Kubernetes Cluster
#7MeanWell has their RS-75-5, which is 60 Watts. Usually around $20.
Re: Anatomy of My Kubernetes Cluster
#8So they don't have to do it at their work.
(Unless they work at a large enough company to justify one.)
Re: Anatomy of My Kubernetes Cluster
#9Re: Anatomy of My Kubernetes Cluster
#10Why 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.