https://github.com/openshift/oadp-operator/issues/1134

probably best to work the details in the issue and PR's

1. Compare CRD version in-cluster to expected CRD version – this would be an ongoing operator reconcile, so that if someone later installed the wrong CRDs as part of another velero/OADP install, current OADP would error out.   A customer would have --force or check a box insisting to install OADP again w/ a different crd version.
2. Some form of notification at install time that warns a user that other OADP versions are already in the cluster.