One server.
A whole cloud,
run
from a Git repo.
Field notes and reference docs for my home Kubernetes cluster — how it's built, why it's built that way, and how to rebuild the whole thing from scratch. Reproducible, documented, and honest about the trade-offs.
How everything connects
From the public internet down to a pod. Traffic enters through the firewall, hits the ingress controller, and every workload is reconciled continuously from Git.
▼
Where to go next
The docs split into the software that runs on the cluster, and the physical & network layer underneath it.
The Homelab Cluster
A single-node k3s cluster running the full self-hosted stack, delivered entirely through GitOps. Per-component docs for everything that runs in-cluster.
- ArgoCD
- Vault
- Longhorn
- cert-manager
- Ingress
- ESO
- Monitoring
- Apps
The Broader Setup
Everything beneath the cluster: physical hardware, VLAN segmentation, DNS, NAS storage, and the firewall rules that tie the whole house network together.
- Hardware
- VLANs
- DNS
- NAS
- Firewall
- Backups
Live component status
A snapshot of the core platform services. Each links through to its reference page.