// the find
bjw-s-labs/home-ops
My home or for-home infrastructure written as code, adhering to GitOps practices. Mirror of https://git.bjw-s.dev/bjw-s/home-ops
A personal homelab Kubernetes cluster managed entirely through GitOps — Flux watches the repo and reconciles everything from cert-manager to Frigate NVR to qBittorrent. It's a mono-repo covering Talos nodes, Ansible playbooks, Docker Compose for edge hosts, and ~40 apps across namespaces. Worth reading if you're building your own k8s-at-home setup and want a well-structured reference.
Renovate is wired up with custom managers and merge groups, so dependency updates are automated without being a free-for-all — the .renovate/ directory shows real thought about which things auto-merge and which don't. The layered network model is solid: Cilium for CNI and NetworkPolicies, BGP for LB IPs, CrowdSec on the edge host for IDS, and Caddy L4 for SNI routing before traffic hits the cluster. Secrets handling uses 1Password Connect plus External Secrets Operator, so no secrets ever land in git. The AI namespace (LiteLLM, Open WebUI, Toolhive, MCP servers) is more fully-formed than most homelab repos that just run Ollama and call it done.
It's one person's infrastructure — the directory layout and tooling choices (mise, just, minijinja, doco-cd) are coherent but idiosyncratic, so copying pieces requires understanding the full mental model first. No disaster recovery documentation: there's Ansible for node provisioning and Flux for app state, but nothing explaining how long a full cluster rebuild actually takes or what the backup story is for stateful apps like Home Assistant and Forgejo. The primary mirror is on a self-hosted Forgejo instance, which means the GitHub repo is a secondary; if you open issues or PRs there you might get silence. Star count (839) overstates discoverability — most value comes from reading the structure, not from any reusable library or tool.