When I set up my cluster from the course, I followed the flux2-kustomize-helm-example layout, which puts the cluster’s entry point in clusters/staging and its overlays in apps/staging, infrastructure/controllers/staging, and so on. That works fine with one cluster. It got confusing once I built a second, VM-based cluster that I actually wanted to use as a staging environment. My production cluster,
Travel has a way of exposing every shortcut in a HomeLab. When I am away with the M5 MacBook, I want to reach the Mac mini and my Skynet cluster as if I never left, without opening a single port on my router. This is Part 1 of a short series on how Cloudflare Tunnel and WARP make that work,
I used to think of Terraform and GitOps as two answers to the same question. They’re really two pipelines, and I run them in two places: Skynet: GitOps only Skynet’s machines already exist, so Terraform has nothing to build. Flux watches my homelab-cluster repo on GitHub, and everything inside the cluster is a file in that repo: the apps, the
In my last post I wrote about the “32TB” backup drive that turned out to be a single SD card behind a lying controller chip. This one covers how I found out it had died. My cluster told me. It just took me a few tries to hear it. Quick recap. Garage holds my Longhorn and CloudNativePG backups, and every
I was scammed, and I knew it was too good to be true. My “32TB” backup drive died on Friday, so I tore it apart. Inside was a single SD card hiding behind a lying controller chip. No real data was lost, since I was only using it as a Garage backup target. Some background. My Skynet cluster runs Garage,