Currently, when you install the Service Binding Operator in the single namespace installation mode, the absence of an appropriate namespace-scoped role-based access control (RBAC) rule prevents the successful binding of an application to a few known Operator-backed services that the Service Binding Operator can automatically detect and bind to. In addition, the following error message is generated: + .Example error message ---- `postgresclusters.postgres-operator.crunchydata.com "hippo" is forbidden:         User "system:serviceaccount:my-petclinic:service-binding-operator" cannot         get resource "postgresclusters" in API group "postgres-operator.crunchydata.com"         in the namespace "my-petclinic"` ---- Workaround 1: Install the Service Binding Operator in the `all namespaces` installation mode. As a result, the appropriate cluster-scoped RBAC rule now exists and the binding succeeds. Workaround 2: If you cannot install the Service Binding Operator in the `all namespaces` installation mode, install the following role binding into the namespace where the Service Binding Operator is installed: + .Example: Role binding for Crunchy Postgres Operator [source,yaml] ---- kind: RoleBinding apiVersion: rbac.authorization.k8s.io/v1 metadata:   name: service-binding-crunchy-postgres-viewer subjects:   - kind: ServiceAccount     name: service-binding-operator roleRef:   apiGroup: rbac.authorization.k8s.io   kind: ClusterRole   name: service-binding-crunchy-postgres-viewer-role ----