Case study / Infrastructure · GitOps
GitOps Homelab
A single-host environment connecting private service delivery, Kubernetes workloads, and recovery paths.
Access & delivery
Private LAN and DNS connect to Forgejo sources, a restricted executor, and a CI runner. Flux reads the documented repositories and reconciles desired state.
Platform & applications
Flux manages Kubernetes resources on Talos, including PostgreSQL, AppFlowy, ingress, and monitoring. These are views of one system, not separate environments.
Data & recovery
Garage stores attachments and backups on the same physical host. An encrypted off-host capture is a separate recovery artifact.
What this does not claim
The single Proxmox host is a shared failure domain, not high availability. Public-gateway activation remains blocked. Registry and custom-image evidence is scoped and does not establish global service availability.
Three architectural views / Archify
One homelab.
Three ways to understand it.
Access, applications, and data form three logical layers. They share one physical host, not three isolated environments. These diagrams describe documented architecture, not live service health.
01 / Access & delivery
Follow private networking, repository sources, CI execution, and GitOps delivery into one host.
Open interactive diagramExplore the diagram here
02 / Platform & applications
Trace Flux reconciliation from the Kubernetes platform to its application workloads.
Open interactive diagramExplore the diagram here
03 / Data & recovery
See how on-host object storage relates to a separate encrypted off-host recovery capture.
Open interactive diagramExplore the diagram here
Continue exploring