Allow Operator to be installed on it's own namespace in OperatorHub

Signed-off-by: pjuarezd <[email protected]>

config/manifests/bases/minio-operator-rhmp.clusterserviceversion.yaml

@@ -13,6 +13,7 @@ metadata:
     marketplace.openshift.io/remote-workflow: https://marketplace.redhat.com/en-us/operators/minio-operator-rhmp/pricing?utm_source=openshift_console
     marketplace.openshift.io/support-workflow: https://marketplace.redhat.com/en-us/operators/minio-operator-rhmp/support?utm_source=openshift_console
     capabilities: "Full Lifecycle"
+    operatorframework.io/suggested-namespace: minio-operator
   name: minio-operator-rhmp.v0.0.0
   namespace: placeholder
 spec:

config/manifests/bases/minio-operator.clusterserviceversion.yaml

@@ -11,6 +11,7 @@ metadata:
     k8sMinVersion: "1.18"
     repository: https://github.com/minio/operator
     capabilities: "Full Lifecycle"
+    operatorframework.io/suggested-namespace: minio-operator
   name: minio-operator.v0.0.0
   namespace: placeholder
 spec:

olm.sh

@@ -97,6 +97,7 @@ for catalog in "${redhatCatalogs[@]}"; do
     echo "  com.redhat.openshift.versions: v4.8-v4.13"
     echo "  # Annotation to add default bundle channel as potential is declared"
     echo "  operators.operatorframework.io.bundle.channel.default.v1: stable"
+    echo "  operatorframework.io/suggested-namespace: minio-operator"
   } >> bundles/$catalog/$RELEASE/metadata/annotations.yaml
 
   echo "clean root level annotations.yaml"