Trivy Scanned My Compromised Server This Morning. It Found Two OpenSSL Bugs.

October 2026: the scanner was healthy, up to date, and looking straight at it.

Last weekend I finally got around to a project that sat on the backburner for months: proper vulnerability scanning for the cluster. Trivy Operator, a built-in server so scans avoid re-downloading the vulnerability database every run, a UI, alert rules, and an accepted-risk register with review dates. The works. I felt pretty good about it. The cluster was finally observed.

The AI That Monitored Your Cluster Just Brought It Down

April 2026 — on the sentinel that decided to burn the house down

“Why can’t I see the new photos?”

That’s how the outage started. Not with a PagerDuty alert or a Grafana dashboard turning red, but with a casual question from my wife. I was already deep in the weeds debugging a glitch in Nextcloud Talk, but as I tried to refresh my own dashboard, the latency didn’t just spike—it vanished. Immich was gone. Mail was gone. The search index was a black hole.

119 commits in one day: what happens when AI meets GitOps without guardrails

January 2026 — a post-mortem on why your branch protections mean absolutely nothing when an AI is at the wheel

---

It started with a reasonable idea

I run a self-hosted Kubernetes cluster. FluxCD manages the entire thing — GitOps, reconciliation loops, the works. Git is the source of truth. It’s a clean, elegant system. You push to main, the cluster updates. Simple.