Ajay Tripathy

Hi @namm2 , loadbalancers outside the scope of kubernetes can further be tracked by integrating your cloud costs and looking at the data on that view.

Currency in opencost is currently only for display; whatever comes out of the pricing URL will be what's in the application, from the time at which it was selected going...

Yes, these can be removed. Good find!

This feels like a pretty major change, can you share a little bit more about the motivation for this change?

Supportive here! This may be a good place to start. https://github.com/opencost/opencost/blob/2f3f98c43b32889069563a696e6582dfbb58d022/pkg/costmodel/csv_export.go#L37

Hi @jagoner what pv metrics are available in Prometheus? Specifically, do you see something like `pv_hourly_cost` coming from opencost?

You will need to scrape opencost metrics such as pv_hourly_cost to see data here. Opencost itself must be scraped for all data to show up in opencost

I'm supportive here, but we would want to make it clear in documentation and potentially even block startup on GCP without this key. I also want to call out that...

We do support workload identities. I guess I'm ok to make the key optional, but we will need a warning that pricing is inaccurate without the key

@aorjoa I have a question on one of your tests-- mind taking another look?