u/openlume — reddlx

When you write it, you already know the relationships.

When you read it, you’re doing this in your head:

That annoyed me enough that I built a small tool for it.

Paste a manifest → it shows the whole thing as a graph + explains it.

You can understand a file in seconds instead of scrolling for minutes.

Runs 100% in your browser.
No backend. Your YAML never leaves your machine. No signup.

What do you think of this?

u/openlume — 9 days ago

▲ 326 r/cloudengineering+1 crossposts

When I read k8s YAML, I am basically doing this:

After doing this too many times, I ended up with something that just visualizes the manifest as a graph and explains it alongside.

It made it way easier to quickly understand what’s going on, especially for larger manifests or stuff I didn’t write.

What do you think of this?

u/openlume — 7 days ago

Not sure if this is just me, but reading someone else’s Kubernetes YAML always feels harder than writing it from scratch.

When I write it, I already know the relationships.
When I read it, I am basically doing this:

After doing this too many times, I ended up hacking together a small tool that just visualizes the manifest as a graph and explains it alongside.

It made it way easier to quickly understand what’s going on, especially for larger manifests or stuff I didn’t write.

What do you think of this?

u/openlume — 10 days ago

I got tired of generic “learn DevOps” roadmaps that just list tools with no order or real projects.

So I put together a DevOps / Platform Engineering roadmap that goes step-by-step from:

It also includes hands-on projects and one capstone where you build a full deployment platform end-to-end.

Made it especially for people trying to break into DevOps / Platform Engineering or level up properly.

Would also love feedback from working engineers. What would you add/remove?

u/openlume — 14 days ago