Home Lab

Overview

This mono repository houses the infrastructure for my homelab. I try to adhere to Infrastructure as Code (IaC) and GitOps practices using tools like Ansible, Terraform, Kubernetes, Flux, Renovate and GitHub Actions.

Layout

📁 bootstrap       # One-time cluster bootstrap (helmfile + kustomize)
📁 kubernetes      # Everything Flux reconciles
├─📁 apps          # The catalogue, grouped by namespace
└─📁 clusters      # One directory per cluster
  └─📁 home
    ├─📁 entrypoint  # The FluxInstance and the root Kustomization
    ├─📁 apps        # What this cluster runs: <namespace>/<app>/ks.yaml
    └─📁 config      # The values this cluster supplies to the catalogue
      ├─📁 namespaces # The Namespaces this cluster creates
      └─📁 secrets   # SOPS, only what is needed before the secret store is up
📁 talos           # Talos machine configs and per-node overrides
📁 terraform       # Providers that live outside the cluster

GitOps workflow

A cluster declares what it runs in clusters/<name>/apps, one Flux Kustomization per app, and apps/ stays a catalogue that knows nothing about which cluster consumes it.

The FluxInstance syncs clusters/home/entrypoint, where the root Flux Kustomization lives.
That applies the rest of clusters/home — the Namespaces and SOPS secrets under config/ and the per-app Kustomizations under apps/.
A Kustomize patch in the cluster root injects the shared defaults (interval, prune, SOPS, substitutions, HelmRelease policy) into every one of them, so each ks.yaml only states name, path and its real deviations.
Each of those applies apps/<namespace>/<app>, waiting on whatever its dependsOn names.