Configuring the catalog source by using the command-line interface (CLI)

Configure the catalog sources by using any of the command-line interface tools- oc or kubectl.

About this task

To configure the catalog source by using the CLI, complete the following steps:

Note: In the following procedure, oc commands are used. The oc commands are interchangeable with kubectl. Hence, if you are connected to a non-OpenShift Kubernetes cluster, ensure that you replace the oc commands with their counterparts.

Procedure

  1. Log in to the Red Hat® OpenShift® Container Platform or Kubernetes cluster. Ensure that you run the oc cluster-info sub-command to verify that the correct cluster information is displayed.
  2. Run the following commands to configure the catalog sources.
    • For catalog_source_sip.yaml: 
      oc apply -f catalog_source_sip.yaml -n catalog_source_namespace
    • For catalog_source_oms_gateway.yaml:
      oc apply -f catalog_source_oms_gateway.yaml -n <catalog_source_namespace>
  3. Verify the installation by running the following commands:
    • For ibm-oms-gateway-catalog: 
      oc get CatalogSources ibm-oms-gateway-catalog -n <catalog_source_namespace>

    • For ibm-sip-catalog: 

      oc get CatalogSources ibm-sip-catalog -n <catalog_source_namespace>
    • If the installation was successful, you see output that is similar to this example output for IBM® Sterling Intelligent Promising Operator catalog.
      NAME                   DISPLAY                 TYPE   PUBLISHER      AGE
ibm-sip-catalog   IBM SIP Operator Catalog      grpc     IBM            50s
    • If the installation failed, an error message is displayed: The following error message is shown for the IBM Sterling Intelligent Promising Operator catalog.

      Error from server (NotFound): catalogsources.operators.coreos.com "ibm-sip-catalog" not found

      To help resolve this error, run the following command to check the pods and CatalogSource resources in the <catalog_source_namespace> namespace:
      oc get catalogsource,pods -n <catalog_source_namespace>
      The output provides information about both the catalog source resources and status of the pods; for example:
      NAME                                                                          DISPLAY                     TYPE   PUBLISHER   AGE
catalogsource.operators.coreos.com/certified-operators                        Certified Operators         grpc   Red Hat     20d
catalogsource.operators.coreos.com/community-operators                        Community Operators         grpc   Red Hat     20d
catalogsource.operators.coreos.com/ibm-sip-catalog                            IBM SIP Operator Catalog    grpc   IBM         48s
catalogsource.operators.coreos.com/ibm-oms-gateway-catalog            IBM OMS Gateway Operator Catalog    grpc   IBM         48s
catalogsource.operators.coreos.com/opencloud-operators                        IBMCS Operators             grpc   IBM         48s
catalogsource.operators.coreos.com/redhat-marketplace                         Red Hat Marketplace         grpc   Red Hat     20d
catalogsource.operators.coreos.com/redhat-operators                           Red Hat Operators           grpc   Red Hat     20d
NAME                                                 READY   STATUS      RESTARTS   AGE
pod/certified-operators-575f586fd8-m2ldh             1/1     Running     0          41m
pod/community-operators-57fd7676ff-sqzgs             1/1     Running     0          15h
pod/ibm-sip-catalog-8534a                            1/1     Running     0          48s
pod/ibm-oms-gateway-catalog-9654g                    1/1     Running     0          48s
pod/marketplace-operator-5fcf68c65c-l8tcg            1/1     Running     0          5d8h
pod/opencloud-operators-wbb9k                        1/1     Running     0          48s
pod/redhat-marketplace-665c9c6db4-hhfkd              1/1     Running     0          41m
pod/redhat-operators-8678ddbc5-6szpp                 1/1     Running     0          4d1h