Home Infra Save

home-infra - Home Cloud via Flux v2 | GitOps Toolkit

GitOps state for my cluster using flux v2

Home infrastructure running: 3x Master Raspberry Pi 4GB + 3x Worker 8GB + 1x 11th Gen Intel Nuc:

• Apps:
  • authelia - SSO server
  • baikal - {Cal,Card}Dav server
  • blocky - DNS proxy and ad-blocker
  • calibre and calibre-web - Lovely E-Book library management
  • docker-mailserver - Postfix + Dovecot + Friends for selfhosted email
  • flood - Pretty and mobile friendly *torrent frontend
  • gitlab - Git + Everything possibly related
  • home-assistant - Home Automation
  • homer - Application Dashboard
  • immich - Self-hosted photo and video management with state-of-the-art ML
  • inspircd - IRC Server
  • jellyfin - Media System
  • my blog - Built with via Gitlab Runners + Buildkitd
  • omada-controller - TP-Link Omada Network Controller
  • thelounge - IRC client
• System:
  • buildkitd - Super efficient container build daemon
  • calico - My CNI of choice which supports BGP peering
  • cert-manager - Automated letsencrypt broker
  • flux2 - Keep cluster in sync with this repo
  • haproxytech ingress - Haproxy.org Ingress controller
  • varnish - Caching reverse proxy
  • vector - Log collection and aggregation
  • victoria-metrics - Lighter prometheus alternative

Secret management

I use mozilla SOPS for secret encryption as it supported out of the box in Flux2. After adding a passwordless secret key to your cluster, add it to your flux-system/gotk-sync.yaml if you want to be able do decrypt secrets in the main flux-system kustomization.

I use a pre-commit hook to ensure that secrets are never pushed unencrypted. Assuming you have a .sosp.yaml the only thing you need to do is:

sops -e -i my-secret.yaml # That's it
sops my-secret.yaml # To edit it directly in your $EDITOR