webb

To give engineering, platform, and other teams a (multi-cloud) cost monitoring that is standardized across all major providers...

I've actually worked with 100+ companies that use labels heavily. It's way more common when you have multiple engineering teams and nobody everybody knows all projects in a cluster. Also, it's common to start with namespace labels which are generally easier to manage.

Yeah, I agree. I actually think that labels are a much better fit for this reference.

> Instead, Kubernetes annotations are meant for sharing information with other colleagues. For example, you may use an annotation to record the phone number of the person responsible for a pod

But it can be super helpful to put owner/contact info for alerting purposes as teams scale.

I also agree that having this metadata on the controller is helpful.

Thanks, simonebrunozzi!

With a growing number of teams using Prometheus-based observability solutions, we've seen more and more integrating Kubecost with their existing Prometheus. The majority still use our bundled offering, which is typically a little easier to setup, but many likely the flexibility to switch if desired.