Platform architecture
The homelab separates infrastructure provisioning, cluster reconciliation, and host configuration. Each layer keeps its desired configuration in Git.
| Layer | Owner | Scope |
|---|---|---|
| Infrastructure | OpenTofu | Proxmox virtual machines, DNS, Talos configuration, and cluster bootstrap |
| Kubernetes | Flux | Platform controllers and applications after bootstrap |
| Hosts | Ansible | Configuration and maintenance of non-Kubernetes hosts |
| Runtime secrets | OpenBao and External Secrets | Secret storage and delivery to applications |
Talos staging reconciles this repository's main branch from
kubernetes/clusters/staging. Production still runs k3s and reconciles the
separate igresc/gitops repository. The production directory here is preparation
for the Talos migration.
The target Talos topology has three control-plane nodes on different Proxmox hosts. Applications share those nodes, and Longhorn provides persistent volumes. Traefik handles ingress behind the public edge. The physical equipment is listed in the hardware overview.
The architecture decisions distinguish the accepted design from its current implementation. Start with repository ownership, Talos lifecycle, and Talos topology.