[HN Gopher] Show HN: Anatomy of My Kubernetes Cluster
       ___________________________________________________________________
        
       Show HN: Anatomy of My Kubernetes Cluster
        
       Author : astefanutti
       Score  : 72 points
       Date   : 2020-03-18 15:29 UTC (7 hours ago)
        
 (HTM) web link (ttt.io)
 (TXT) w3m dump (ttt.io)
        
       | asdfman123 wrote:
       | More software engineers should build Kubernetes clusters like
       | this at home...
       | 
       | So they don't have to do it at their work.
       | 
       | (Unless they work at a large enough company to justify one.)
        
       | captn3m0 wrote:
       | If you'd like to do something similar, check out the Turing Pi,
       | which uses RPI compute modules and runs off a ATX power supply.
       | 
       | https://turingpi.com/
        
       | tyingq wrote:
       | _" 59 Watts, That's well above the power supplied by any AC mains
       | to 5V DC external power supply I could find"_
       | 
       | MeanWell has their RS-75-5, which is 60 Watts. Usually around
       | $20.
        
       | zulu-inuoe wrote:
       | Real question coming from a non-k8-user. What would you use
       | something like this for? Server hosting or?
        
         | bashinator wrote:
         | 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.
        
       | m0zg wrote:
       | 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.
        
         | rubiquity wrote:
         | Because tinkering is fun and fun is good.
        
           | m0zg wrote:
           | It just seems like there are much more interesting projects
           | available for "tinkering" than building a slow, barely usable
           | Kubernetes cluster.
        
             | moondev wrote:
             | Like what? Interested to hear what you deem interesting
             | enough to tinker on.
        
       | tra3 wrote:
       | 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.
        
         | rcarmo wrote:
         | 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 :)
        
       | ablekh wrote:
       | Nice write-up.
        
       | rcarmo wrote:
       | 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...)
        
       ___________________________________________________________________
       (page generated 2020-03-18 23:00 UTC)