When installing the 3rd csi driver operator like efs/smb/secrets-store csi driver operator and NOT install the clustercsidriver resource, the logs is full of "clustercsidrivers.operator.openshift.io \"xxxxxxxxx\" error like:

E0331 05:47:08.327004       1 base_controller.go:279] "Unhandled Error" err="SambaDriverGuestStaticResourcesController-StaticResources reconciliation failed: clustercsidrivers.operator.openshift.io \"smb.csi.k8s.io\" not found"
E0331 05:47:08.332347       1 base_controller.go:279] "Unhandled Error" err="SambaDriverControlPlaneStaticResourcesController-StaticResources reconciliation failed: clustercsidrivers.operator.openshift.io \"smb.csi.k8s.io\" not found" 


For the default-installed csi driver, the clustercsidriver resource is installed by CSO, so no such error there.


I'm not sure if it is worth to fix it and how much effort it spends like if library-go supports or we could apply clustercsidriver inside the operator. Just try to raise it to see if it would be tolerated. 

Take smb-csi-driver-operator as example, there are 300~ errors in 45 mins
$ oc -n openshift-cluster-csi-drivers logs smb-csi-driver-operator-58d547b9c-848bc | grep "reconciliation failed"|  wc -l
307
     

4.18 and other releases     

Always

1. create 3rd csi driver operator but not install the clustercsidriver
2. check the log from the operator