Infrastructure I live with
Two homes, a cloud hub, and services my family actually depends on.
This is where I build and operate infrastructure as code, Kubernetes, networking, security, and observability. When photos or the smart home stop working, it is more than a lab exercise.
Two homes, one pattern, one cloud hub
Both homes follow the same service pattern. Oracle Cloud adds an independent view and a place to coordinate the wider system.
From everyday services to the infrastructure beneath
Access · Identity checks
Tunnel · Outbound connections
GitHub Actions · Checks
Argo CD · Application delivery
Family services run across both homes. Cloudflare handles remote access, Git and CI support controlled changes, and an Oracle Cloud hub provides monitoring and coordination. Select a path to explore how the layers work together.
Cloudflare Access checks identity; Tunnel reaches services over connections initiated from home. Selected services also have a local path through split DNS, so access follows the appropriate route at home or away.
OpenTofu defines infrastructure and the access layer. GitHub Actions checks configuration and manifests using a cloud-hosted runner; Argo CD reconciles applications into K3s. Infrastructure plans are reviewed before apply.
VictoriaMetrics and Grafana provide metrics and a view across both homes. The cloud hub probes services from outside, and alerts surface problems. An additional external check watches the monitoring path itself.
Rebuild it from code
I rebuilt the cloud hub from its infrastructure definitions. It was a practical test of bringing the operations layer back, beyond the initial setup.
Home is where I keep learning: deployments, failures, access, and data — with responsibility for services we use every day.