Crash when two resources of the same kind with the same name exist in different namespaces. about opencost HOT 4 CLOSED

Good catch, Luis. This is definitely an issue. It actually looks like you were for some reason provisioned a claim that has two storageclasses: standard-disk and <none>. I haven't seen this yet.

Is there any chance you could share the result to this Prometheus query? kube_persistentvolumeclaim_info This should help us pinpoint the issue a little faster.

An easy fix would be to exclude storageclass =<none> but it's not clear this addresses the underlying problem.

from opencost.

sorry, I've ended up deleting the extra pvc that had been created by mistake in the default namespce but I can try to reproduce this with some other resource type.
What I had was two pvcs one in the kube-opex-analytics namespace with storage class set to standard-disk and another one with the same name on the default namespace with no storage class set.

from opencost.

Got it, this is helpful. We should now be able to recreate but will follow up if for some reason we can't!

from opencost.

I was able to recreate! PR out for review.

from opencost.