Description of problem:
manila csi driver install failed for manila csi driver operator did not installed in manila-csi namespace

Version-Release number of selected component (if applicable):
4.5.0-0.nightly-2020-05-17-235851
"Operator Version: 0.0.1"

How reproducible:
Always

Steps to Reproduce:
1. Login into the webconsole
2. Install csi-driver-manila-operator from operator hub into manila-csi-1 namespace
3. Create manilacsi instance to install manila csi driver

Actual results:
1. No driver is installed.

2. cluster operator cloud-crendtial is in degraded status.
$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.5.0-0.nightly-2020-05-17-235851   True        False         24h     Error while reconciling 4.5.0-0.nightly-2020-05-17-235851: the cluster operator cloud-credential is degraded

check the operator log, we can see:
{"level":"info","ts":1589863185.4884112,"logger":"controller_manilacsi","msg":"No installer-cloud-credentials secret was found in manila-csi namespace. Retrying...","Request.Namespace":"manila-csi-1","Request.Name":"manilacsi-1"}

When create manila-csi namespace manually, the installer-cloud-credentials secret in created in manila-csi namespace, the operator still report can not find this secret.

Expected results:
Install manila csi driver successfully.
1. If we want the manila csi driver operator must be installed in manila-csi namespace, then when we insall the operator in other namespace, the operator installation should be failed and report clear err msg.
2. If we can install manila csi driver operator in any namespace, the operotor should create manila-csi namespace if the namespace is not exist and ensure the manali csi driver is installed in manila-csi namespace sucessfully.

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info: