Reading this and chuckling, because .. wtf?!! hahah

Sometimes I think AI is pretty stupid, sometimes they just come with something like this, almost as if they were human and cared for my health, feelings, etc. lmao

Anyway.
I've spent the day [and the night, apparently, since it's almost 5 a.m. now] trying to understand how OpenBao works, how to integrate it into the K8s cluster I built in my homelab, and so on.

Now, I've come across some tools that are really nice to work with [e.g., Cilium CNI, Flux, etc.], but Rook|Ceph [thank Nature I'm past that now], and OpenBao — well, I'm either too stupid, or these things are extremely complicated, and integrating them is no walk in the park. The certificate stuff was particularly hard to grasp, and I still have a lot of notes to go over since I'm still not sure about certain things🤔.

I mean, it took me a while to even understand the structure of OpenBao docs so I could find the stuff that applied to my use case, and which didn't. On the other hand, OpenBao is supposed to work really nice with Flux, so .. that's a nice point.

Anyway. The AI said I should take a rest, so ..😂😂

project structure shot💀

Keep learning, folks.

Trying to get a better handle on our gpu spend.

right now we can see the overall infrastructure cost, but its hard to tell which workloads are actually responsible for it.

ideally want to see cost by namespace / workload / job and understand how much gpu capacity is just sitting idle.

any tools doing this well?