I've been doing HomeLab and HomeLab-adjacent things for over 10 years at this point. My first experience in the space was a Raspberry Pi 2 that I used for a few years to run various services such as Pi-Hole, CUPS, and numerous other software. Since then, my lab has had

Starting a new Cloud/HomeLab blog at this domain - let me know if you want a contributor invite!

  • @[email protected]
    2•9 months ago

    I get what the author is talking about with losing trust in your services when they are unavailable. I have found that a Raspberry Pi 3/4 cluster running k3s utilizing NAS storage has very good uptime and honestly I think my internet service goes down more than my homelab services.

    • @[email protected]OPM
      2•9 months ago

      Thanks! I find most of the issues occur during upgrades to services, but that is to be expected.

      My internet service is usually more of an issue than most services I run. Though some things take longer to get tweaked and running well and that can cause issues.

      • @[email protected]
        1•9 months ago

        Upgrades to services - that’s why I run dev namespaces and copy over my production shares to dev and utilize zfs snapshotting.

        I haven’t set up testing yet and only just started with prometheus monitoring but so far things run pretty well.

          • @[email protected]
            1•9 months ago

            I toyed with dev domain but ended up using namespace.tld and postfixing -dev to my namespace so it works out to service.tld and service-dev.tld.

              • @[email protected]
                1•9 months ago

                I have automated traefik to route the traffic, it sets the dns and ingress route. I’m also doing as you suggested for service to service connections.

                • @[email protected]OPM
                  2•9 months ago

                  That makes sense!

                  Have you played with anything like Istio to secure in-cluster communications? I think Hashicorp Consul can do something similar to encrypt service to service communications.