Fixes doc error: namespace name must have changed (#2839)

$ kubectl -n local get deployments
No resources found in local namespace.

$ kubectl -n olm get deployments
NAME               READY   UP-TO-DATE   AVAILABLE   AGE
catalog-operator   1/1     1            1           6m11s
olm-operator       1/1     1            1           10m
packageserver      1/1     1            1           10m

Signed-off-by: Brett Tofel <[email protected]>

Signed-off-by: Brett Tofel <[email protected]>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 665c25b3c42126b896791d8af9589fab2948080d

Author: bentito

pkg/manifests/csv.yaml

@@ -5,7 +5,7 @@ metadata:
   name: packageserver
   namespace: openshift-operator-lifecycle-manager
   labels:
-    olm.version: 0.0.0-256c96db7ec26300295e764b4ab59a1c22879ed8
+    olm.version: 0.0.0-f8dd7c4e6b8762e41dd59f9e727c52acd9cffe59
     olm.clusteroperator.name: operator-lifecycle-manager-packageserver
   annotations:
     include.release.openshift.io/self-managed-high-availability: "true"
@@ -159,7 +159,7 @@ spec:
                                 - packageserver
                         topologyKey: "kubernetes.io/hostname"
   maturity: alpha
-  version: 0.0.0-256c96db7ec26300295e764b4ab59a1c22879ed8
+  version: 0.0.0-f8dd7c4e6b8762e41dd59f9e727c52acd9cffe59
   apiservicedefinitions:
     owned:
       - group: packages.operators.coreos.com

staging/operator-lifecycle-manager/doc/install/install.md

@@ -25,7 +25,7 @@ This command starts minikube, builds the OLM containers locally with the minikub
 $ make run-local
 ```
 
-You can verify that the OLM components have been successfully deployed by running `kubectl -n local get deployments`
+You can verify that the OLM components have been successfully deployed by running `kubectl -n olm get deployments`
 
 **NOTE** It is recommended for development purposes and will use the source locally