Attempt to install Data Grid Operator in MultiNamespace install mode no longer works with 4.15 using the same configuration as with 4.14.
    

Always
    

    1. Install Data Grid Operator in a specific namespace
    2. Edit Operator group so it targets different namespace
    

W0118 12:49:43.247738 1 reflector.go:324] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:158: failed to list *v1.Infinispan: infinispans.infinispan.org is forbidden: User "system:serviceaccount:datagrid-operator:infinispan-operator-controller-manager" cannot list resource "infinispans" in API group "infinispan.org" in the namespace "datagrid-cluster"
W0118 12:49:43.247760 1 reflector.go:324] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:158: failed to list *v2alpha1.Cache: caches.infinispan.org is forbidden: User "system:serviceaccount:datagrid-operator:infinispan-operator-controller-manager" cannot list resource "caches" in API group "infinispan.org" in the namespace "datagrid-cluster"
E0118 12:49:43.247767 1 reflector.go:138] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:158: Failed to watch *v1.Infinispan: failed to list *v1.Infinispan: infinispans.infinispan.org is forbidden: User "system:serviceaccount:datagrid-operator:infinispan-operator-controller-manager" cannot list resource "infinispans" in API group "infinispan.org" in the namespace "datagrid-cluster"
E0118 12:49:43.247772 1 reflector.go:138] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:158: Failed to watch *v2alpha1.Cache: failed to list *v2alpha1.Cache: caches.infinispan.org is forbidden: User "system:serviceaccount:datagrid-operator:infinispan-operator-controller-manager" cannot list resource "caches" in API group "infinispan.org" in the namespace "datagrid-cluster"
    

Expected results are that the Operator will be normally able to manage targetNamespace as specified.
    

SingleNamespace and AllNamespace mode work fine. Given the MultiNamespace install mode works fine with 4.14 I assume there is either a regression or a change in requirements. Nevertheless I wasn't able to find the root cause, therefore opening an issue against OCPBUGS.