r2k1

Looks like there is an option to configure label aggregation. Something similar can be done for other options.

I would probably add something like: ``` EXPORT_CSV_COLUMNS=Date,ControllerKind,ControllerName,TotalCost ``` And if it's not specified, set the currently exported columns. I think it will be the most flexible options covering most...

How you would like to present this information? Adding extra prometheus metrics may not be necessary since querying them is already straightforward. I would like to see this information in...

It appears that the node_cpu_hourly_cost Prometheus metric is not returning any data. This metric is crucial for determining the date range of stored data in Prometheus to avoid incomplete data....

With the default prometheus installation you should be able to use something close to the next command to access the prometheus UI. ```bash kubectl -n kube-system port-forward svc/my-prometheus-server 9090:9090 ```

I suspect it can be solved by changing opencost deployment ```yaml apiVersion: apps/v1 kind: Deployment metadata: name: opencost namespace: opencost # ... spec: # ... template: # ... spec: #...

It would be nice to have a more automated way, but here is what I've done. From what I've seen the usage is more or less linear with cluster size....

If you want to test a change and iterate on it. Here is a hackish solution I used: https://github.com/opencost/opencost/compare/develop..memtest I usually just run memory profiler for a single test in...

Sorry, I didn't measure properly how label count affects it.

Additional Notes: kube-state-metrics employs certain strategies to optimize memory usage: - Instead of Informers, it uses [Reflector](https://pkg.go.dev/k8s.io/[email protected]/tools/cache#Reflector) instead of Informer, allowing a direct transformation from a Kubernetes object to a...