Matt Ray

Did you have your CLOUD_PROVIDER_API_KEY set? You can do that from an environment variable or with the Helm chart. https://www.opencost.io/docs/configuration/gcp#configuring-gcp-pricing

I've updated the docs to focus the required steps per-cloud provider. The GCP instructions include the CLOUD_PROVIDER_API_KEY steps: https://www.opencost.io/docs/configuration/gcp#add-the-gcp-api-key-to-opencost

@sfrolich What's different between your 2 environments?

> So @mattray what do you think could cause it to eventually succeed? Really hard to tell. Is it possible someone updated permissions on a role between deployments?

Could you try 1.110.0 and see if the issue persists? Since this one's been closed maybe we should start a new issue against 1.110.0 and we'll try to clear the...

I'd assume we could do this with the OpenCost Helm Chart, how does Kubecost do it?

`Failed to load auth secret, or was not mounted: Secret does not exist` indicates that the `secret` you referred to wasn't added. https://www.opencost.io/docs/configuration/#cloud-costs I'm refreshing the Installation docs right now...

Thanks for highlighting this, I've referred it to Kubecost Engineering to investigate, but we'd welcome a PR.

`accumulate` isn't documented in the API (https://www.opencost.io/docs/integrations/api#allocation-api) because it currently doesn't work in OpenCost. My testing showed what yours showed, so I left it out of the documentation. My apologies...

@Faustinekitten Thanks for raising this. It looks like they're missing from the available choices and not listed in the API: https://github.com/opencost/opencost/blob/develop/ui/src/Reports.js#L48 https://www.opencost.io/docs/integrations/api#a_aggregate If my understanding of the Allocation code is...