Excited to share my latest open-source project: KubeCost Guardian

This looks like a useful direction, especially for teams that already have AKS cost data but need better actionability.

A couple of design points I would be interested in seeing are: does it work with read-only Azure RBAC/managed identity, how does it handle shared cluster costs, and can recommendations be mapped back to namespace/team labels? That mapping is usually what turns cost visibility into something teams can actually own.

It may also be worth adding a suppression or approval workflow for recommendations. Some workloads look wasteful from CPU/memory averages, but are intentionally over-provisioned for burst, latency, or compliance reasons. Capturing that context would make the tool much more useful in real platform teams.