At home, four small Intel N150 machines run a Kubernetes cluster with 59 applications
on it. It hosts my own GitLab, my password manager, my media server, a Fediverse
instance and a site where people learn Go in the browser.
It also runs the house. Every quarter of an hour it reads the electricity price and
decides whether to heat the water boiler. That job used to be a cron script on a
Raspberry Pi. It keeps a dashboard for my car too. That one can only read: the build
fails if the code could ever send the car a command.
All of it is declarative and every change is a pull request. YAML lint, helm template,
kubeconform, per‑chart values rendering and a KSOPS hash guard must pass in CI
before merge.
Tools the homelab runs on and how each is set up
| Tool |
Setup |
| Talos Linux |
A cluster of four nodes: three control-plane and one worker, on Intel N150. |
| Argo CD |
App-of-apps with 59 applications and secrets in SOPS with KSOPS. |
| Prometheus, Grafana and Loki |
Alloy ships the logs, retention is 60 days, and the dashboards are my own. |
| Traefik |
TLS 1.3 only, with ECDSA P-384 certificates from Let's Encrypt over ACME and HSTS preload. |
| external-dns |
Works with Cloudflare, plus cron jobs for DANE with TLSA and for CAA, with SOPS-encrypted credentials. |
| OpenTofu |
Hetzner edge nodes, HAProxy ingress to Tailscale, and infrastructure as code end to end. |