Posts

How the pieces fit together Cloudflare Tunnel exposes the individual services — the Kubernetes app, ArgoCD, Grafana — as hostnames on christiehome.work. Traffic comes in through a UniFi Dream Machine on its own VLAN, and from there splits two ways: a two-node Raspberry Pi K3s cluster running the workloads and GitOps tooling, and a separate Proxmox host running the DevOps VMs used for day-to-day work. A Synology NAS provides iSCSI-backed persistent storage to the cluster. ...

A small end-to-end build: a Cloudflare Worker, the GraphQL Analytics API, and a Hugo site, wired together to show real visitor stats on every page.

I stripped away Docker, containerd, and Podman entirely and built a working container using only core Linux primitives — namespaces, OverlayFS, and cgroups — to understand exactly what container runtimes are automating under the hood.

What This Post Is This blog exists to document my homelab DevOps work as I make the move from IBM Maximo consulting into DevOps engineering. Before writing about Kubernetes and GitOps, I figured the first post should document how the blog itself works — because the deployment pipeline is itself a DevOps project. The Stack Component Tool Static site generator Hugo Theme PaperMod Source control GitHub CI/CD + hosting Cloudflare Pages Domain Cloudflare Registrar (christiehome.work) Local editor Neovim / VS Code How It Works End to End Write locally in Markdown Every post is a plain Markdown file sitting in content/posts/. I write locally using Neovim or VS Code. No CMS, no browser editor, no login required. ...