Geiser's Cloud

Overengineering is usually framed as a “software developer problem”: too many layers, too many abstractions, too many features nobody asked for.

A lightweight, three-node S3 cluster that doubles as a rock-solid backup target Garage v2.x is almost here—Release Candidate 1 is already out of the oven—so it feels like the perfect moment to write up a clean, reproducible installation guide.

When a new capability feels like magic, the only reasonable reaction is to ask ‘how can I wire this into my own toys?’”

Being on-call is the tax you pay for running software in production.

I’m coming up on ten years with DevOps in my job title, badge, Slack handle—whatever.

“Wait… why is our cluster at 8 % CPU and we’re still paying a fortune?”

Some months ago, my at-home production cluster started paging me with the classic Volume /var/loki ≥ 90 % alert.

Never send a human to do a machine’s job The quote is from The Matrix, but in 2025 you’ll hear a variant of it every time the Kubernetes community starts talking about Operators.

I know what you're thinking—no, I didn't actually DDoS Amazon EKS and Google GKE.

It all started early in 2023—an ordinary morning interrupted by a not-so-ordinary phone call.

Scientists investigate that which already exists; Engineers create that which has never existed.

"Aren't you a developer if one of your projects is managing software updates?"

I’ve always been as attracted to computers as iron is to a magnet.

Sometimes technical challenges just come out of nowhere—and ruin your day (or months).

Scientists investigate that which already exists; Engineers create that which has never existed.