Skip to content

Field notes from a Kubernetes homelab

Build it. Operate it. Understand it.

A heterogeneous cluster, local AI, and the decisions that hold them together. Follow the builds, investigate the failures, and take the useful parts home.

Start here

Three ways into the project
operating

Operating on Green

Five ways a healthy dashboard lies — wrong artifact, unconsumed signal, out of scope, stale view, never applied — and the command that checks each

15 min read
papers

Why Run Your Own Cluster in 2026?

Three philosophies dominate infrastructure decisions in 2026: cloud (pay the bill, ignore the metal), managed homelab-as-code (own the iron, outsource lifecycle), and DIY…

8 min read

What are you working on?

All topics

Latest writing

Retrieval on the Idle iGPUs

Embeddings and reranking on my control plane's idle Arc iGPUs via Kubernetes DRA, plus the CPU control arm that decided whether the accelerator earned it

Operating on Green

Five ways a healthy dashboard lies — wrong artifact, unconsumed signal, out of scope, stale view, never applied — and the command that checks each

Recently updated

Why Build a Kubernetes Homelab?

The motivation behind Frank, the Talos Cluster — learning enterprise infrastructure and building interesting projects on your own hardware.

Paperclip — An AI Agent Orchestrator on Frank

Deploying Paperclip — an AI orchestrator that organises agents into virtual companies with org charts and budgets — alongside Sympozium, to compare two fundamentally different agentic paradigms.

Operating on Paperclip

Checking Paperclip health, database access and secret sync, handling the RWO PVC constraint, and bootstrapping the pure-upstream instance after the 2026-10 fresh start.

Operating on Cluster & Nodes

Day-to-day commands for checking cluster health, managing Talos nodes, and debugging Cilium networking on Frank — including the real failure patterns the gotcha docs cover.

Follow a series