Document URL: 
https://docs.openshift.com/container-platform/4.3/operators/olm-restricted-networks.html#olm-restricted-networks-operatorhub_olm-restricted-networks


Section Number and Name: 
4. Verify the CatalogSource and package manifest are created successfully:

Describe the issue: 
`oc adm catalog build`, `oc adm catalog mirror` and `oc apply -f ./manifests` don't create the CatalogSource object automatically.
But, we list the below validation info in step 4, it's confusing.

# oc get pods -n openshift-marketplace
NAME READY STATUS RESTARTS AGE
my-operator-catalog-6njx6 1/1 Running 0 28s
marketplace-operator-d9f549946-96sgr 1/1 Running 0 26h

# oc get catalogsource -n openshift-marketplace
NAME DISPLAY TYPE PUBLISHER AGE
my-operator-catalog My Operator Catalog grpc 5s


Suggestions for improvement: 
I know we have already a step to describe the CatalogSource creation in https://docs.openshift.com/container-platform/4.3/operators/olm-restricted-networks.html#olm-testing-operator-catalog-image_olm-restricted-networks

But, it's better if we add a step before step 4 to introduce the CatalogSource object creation.


Additional information: 
For example:
$ cat CatalogSource.yaml
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: my-operator-catalog
  namespace: openshift-marketplace
spec:
  sourceType: grpc
  image: <registry_host_name>:<port>/<namespace>/redhat-operators:v1
  displayName: My Operator Catalog
  publisher: grpc