About — Podo Stack

Tired of the endless stream of new tools?

Every week someone ships yet another project that’ll “make your life easier.” Yeah, right. Half of them are half-baked. A third get abandoned within six months. The rest solve problems you probably don’t have.

So I filter. I use things, read the source, watch how they behave when everything breaks. Sometimes I find something worth sharing.

Hey, I’m Ilia.

Engineer. I run production clusters, debug eBPF at 3am, read RFCs for fun. That last one sounds weird, I know — but I actually find it interesting why things work the way they do.

Why Podo (포도)?

It’s Korean for grapes. They grow in clusters. Like pods in Kubernetes — you get the idea.

But it’s not just about the name. Grapes need to ripen. Tools do too. That shiny project from Hacker News last week? Give it a year. The one that’s been quietly maintained for three years with boring changelogs? That’s probably ready for prod.

I dig through this jungle looking for what’s Ripe for Prod. The stuff that’s actually ready.

What to expect

No “10 kubectl commands you need to know.” You can Google that.

Different stuff. Why kube-proxy doesn’t actually proxy anything. What happens between kubectl apply and your pod starting — there’s a lot going on there, by the way. Where the name etcd comes from. That kind of thing.

Sometimes I’m wrong. Sometimes I change my mind. I’ll tell you when I do.

New issues drop once a week. Short, to the point.

If you’re a mid-to-senior engineer who’s tired of surface-level content — welcome.

— Ilia