Modern IT infrastructure, in five pillars
The framework I use to keep infrastructure sane: five pillars on four foundations, every component a CI wired to the rest.
Notebook
Real findings from the work and the homelab — what I'm building, breaking and fixing along the way.
The framework I use to keep infrastructure sane: five pillars on four foundations, every component a CI wired to the rest.
A private CA as the single SSH trust root: short-lived certs for humans (SSO+MFA), 10-minute ones for machines, and host certs that kill known_hosts TOFU.
Defense-in-depth at the homelab edge with CrowdSec: known-bad IPs dropped at the door, then an in-band WAF reads what's left. And why it's deliberately fail-open for now.
An internal site that wouldn't load, a resolver that was never asked, and the dead-IP query that proved a 'helpful' gateway was answering DNS behind my back.
Wiring our identity agent into a secrets manager without handing it the kingdom: read-only by default, segregation of duties, and writes you have to mean.
From a typed request to a guarded action against a real system, a walk down the stack that turns Claude Code into a fleet of homelab operators: the CLI, the shared agent-core, the agents, their skills, and the actions they perform.
A simple question (do our agents need MCP?) that quietly turned into a clearer picture of skills, MCP servers, and the identity layer sitting underneath both.
Building a DNS skill for our network agent, and the two-layer permission model that hid our zones in plain sight.
Standing up an authoritative internal resolver as code: split-horizon, encrypted upstreams, and the moment the new DNS box couldn't resolve its own installer.
Teaching my agent to update Docker stacks within policy: including the source-built ones that have no image to pull.
Building the cloud-init template every VM clones from. And learning the hard way that UEFI + cloud images + a serial console hides your boot failures.
The first phase changes nothing. It just reads live state and proves how wrong the plan already was. Discovery is the cheapest phase and the most valuable.
Starting a phased, infrastructure-as-code rebuild of the homelab, and pairing with an AI agent that does the typing while I keep the judgement.
The five-minute baseline I apply to every new server before it goes anywhere near a network.
Segmentation isn't just an enterprise checkbox. Here's how I split a single Proxmox node into safe zones.
A critical-auth VLAN so a dead RADIUS server doesn't take a whole floor offline.