When kubernetes-event-exporter is deployed on a cluster with many CRD (custom resource definitions) and its default clusterrole doesn't account for them, it then starts logging a ton of errors and this can cause problems (like saturation of storage if you are ingesting your logs from the kubernetes cluster).
I think a better approach is to log errors involving CRD at the debugging level. So you can fix your clusterrole and avoid being overwhelmed by errors.
When kubernetes-event-exporter is deployed on a cluster with many CRD (custom resource definitions) and its default clusterrole doesn't account for them, it then starts logging a ton of errors and this can cause problems (like saturation of storage if you are ingesting your logs from the kubernetes cluster). I think a better approach is to log errors involving CRD at the debugging level. So you can fix your clusterrole and avoid being overwhelmed by errors.