Description of problem:
When subscribed to certified Couchbase-operator only Role and RoleBindings are created by installplan. Couchbase-operator requires permissions for get and watch persistentvolumes, persistentvolumes are Cluster Scope object, therefore Cluster Role and Cluster RoleBinding should be created.

Couchbase-operator CSV has persistentvolumes verbs listed under permissions section, which is wrong as 'permissions' object in CSV CR is reponsible only for creating namespace roles and rolebindings, as mentioned persistentvolumes is cluster scope object, therefore CSV should be patched with "clusterPermissions" section where verbs get and watch should be added for persistentvolumes object. Even when catalog is patched manually with correct CSV seems like the version of installed OLM operator does not understand clusterPermissions as still installplans are not creating needed ClusterRole and ClusterRoleBinding.

This prevents couchbase-operator from installing couchbase with persistent-volumes which defeats the whole purpose of using couchbase-operator cause who want's database server without ability to persist data

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Subscribe to Couchbase-operator in namespace allowed for OLM operators
2. Apply CouchbaseCluster CRD with persistentvolumes defined

Sample cb-pv CR taken from couchbase documentation:

```
apiVersion: couchbase.com/v1
kind: CouchbaseCluster
metadata:
  name: cb-cluster-pv
spec:
  baseImage: registry.connect.redhat.com/couchbase/server
  version: 5.5.3-3
  authSecret: cb-example-auth
  adminConsoleServices:
    - data
  cluster:
    dataServiceMemoryQuota: 512
    indexServiceMemoryQuota: 512
    searchServiceMemoryQuota: 512
    eventingServiceMemoryQuota: 512
    analyticsServiceMemoryQuota: 1024
    indexStorageSetting: memory_optimized
    autoFailoverTimeout: 120
    autoFailoverMaxCount: 3
    autoFailoverOnDataDiskIssues: true
    autoFailoverOnDataDiskIssuesTimePeriod: 120
    autoFailoverServerGroup: false
  buckets:
    - name: test1
      type: couchbase
      memoryQuota: 128
      replicas: 1
      ioPriority: high
      evictionPolicy: fullEviction
      conflictResolution: seqno
      enableFlush: true
      enableIndexReplica: false
  securityContext:
    fsGroup: 1001940000
  servers:
    - name: west-2a
      size: 1
      services:
        - data
        - index
      serverGroups:
        - us-west-2a
      pod:
        volumeMounts:
          default: us-west-2a
          data: us-west-2a
  volumeClaimTemplates:
    - metadata:
        name: us-west-2a
      spec:
        storageClassName: "gp2-us-west-2a"
        resources:
          requests:
            storage: 10Gi
```
Actual results:
Couchbase-operator unable to start couchbase pod with following error in logs:
time="2019-02-12T18:47:32Z" level=info msg="Creating a pod (cb-cluster-pv-0000) running Couchbase 5.5.3-3" cluster-name=cb-cluster-pv module=cluster
time="2019-02-12T18:47:39Z" level=info msg="deleted pod (cb-cluster-pv-0000)" cluster-name=cb-cluster-pv module=cluster
time="2019-02-12T18:47:39Z" level=error msg="Cluster setup failed: fail to create member's pod (cb-cluster-pv-0000): unknown (get persistentvolumes)" cluster-name=cb-cluster-pv module=cluster
time="2019-02-12T18:47:39Z" level=warning msg="Fail to handle event: ignore failed cluster (cb-cluster-pv). Please delete its CR"

Additionally no ClusterRole and ClusterRoleBinding is created for couchbase-operator serviceaccount which causes the above error in logs

To manually mitigate that problem cluster role needs to be created with get and watch permissions for persistentvolume and binded to couchbase-operator serviceaccount, only then couchbase-operator is able to successfully start couchbase pods backed by pvs

Expected results:
Couchbase pods start normally when CSV has proper clusterPermissions, cause during Subscription to couchbase-operator installplan is installing proper clusterrole and clusterrolebinding as well

Additional info:
All this is cause probably by two things old OLM that does not support clusterPermissions in CSV CR, and bad CSV CR that list permissions for persitentvolumes in permissions instead of clusterPermissions object in that CR.

OLM should be updated to 0.7.x and CSV patched to list clusterPermissions