<story><title>Anatomy of My Kubernetes Cluster</title><url>https://ttt.io/anatomy-of-my-kubernetes-cluster</url></story><parent_chain></parent_chain><comment><author>asdfman123</author><text>More software engineers should build Kubernetes clusters like this at home...&lt;p&gt;So they don&amp;#x27;t have to do it at their work.&lt;p&gt;(Unless they work at a large enough company to justify one.)</text></comment>
<story><title>Anatomy of My Kubernetes Cluster</title><url>https://ttt.io/anatomy-of-my-kubernetes-cluster</url></story><parent_chain></parent_chain><comment><author>rcarmo</author><text>This is neat. I&amp;#x27;ve been doing the same with Pi 1s and 2s for a few years (&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;rcarmo&amp;#x2F;raspi-cluster&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;rcarmo&amp;#x2F;raspi-cluster&lt;/a&gt;) but stopped short of upgrading to 3s and 4s because of heat&amp;#x2F;power&amp;#x2F;cost.&lt;p&gt;I&amp;#x27;ve found that it is possible to run k3s on SD cards quite well if you&amp;#x27;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.&lt;p&gt;(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&amp;#x27;s much easier to get traefik working in Swarm...)</text></comment>