murphd40

I'm also seeing this behaviour: ``` $ kubectl get po NAME READY STATUS RESTARTS AGE catalog-operator-7f6fdbc478-6b8j2 1/1 Running 0 110m olm-operator-7f5fbcf9f9-bhljf 1/1 Running 0 110m operatorhubio-catalog-v5w7b 0/1 CrashLoopBackOff 7 14m...

Looks like my issue will be fixed in the next release: This [PR](https://github.com/operator-framework/operator-lifecycle-manager/pull/2791) tackles the issue 👍 Thanks

Hi @rexagod . In that case would it be better to add logic to remove duplicates from the `resources` list?

Hi @ikarlashov @rexagod. Apologies for the delay. I have updated the PR as suggested. However, when I run ``` go run main.go --port=8080 --telemetry-port=8081 --kubeconfig=$KUBECONFIG \ --custom-resource-state-config='{"spec":{"resources":[{"groupVersionKind":{"group":"operators.coreos.com","version":"v1alpha1","kind":"ClusterServiceVersion"},"metrics":[{"name":"csv_info","help":"Cluster Service Version install...

I have also encountered this issue. It was not present in 8.7.0 For me, it occurs when I specify a `--custom-resource-state-config` and include it in `--resources` ``` $ go run...