Preparing and configuring the catalog source for Kubernetes cluster

To set up Kubernetes Service cluster and support installation of operators, connect a command line environment to the cluster. The IBM Kubernetes administrator must create the catalog source that registers the Rhapsody Systems Engineering operator. After the registration, you can install the operator by using the command line.

1. Prepare the catalog source manifest. From your local computer, create catalog_source.yaml by using the following content.

   apiVersion: operators.coreos.com/v1alpha1
       kind: CatalogSource
       metadata:
           name: ibm-rse-catalog
           namespace: <catalog_source_namespace>
       spec:
           image: cp.icr.io/cpopen/ibm-rse-operator-catalog:latest
           sourceType: grpc
           updateStrategy:
               registryPoll:
                   interval: 10m

   Note: The updateStrategy must be adjusted to the desired frequency for the operator to check the registry for future updates. In the example, the operator checks for new updates every 10 minutes. To minimize the frequency of checks and reduce resource utilization, you can set the interval to a higher value if required.
2. Configure the catalog source by using command line.
   1. Run the following command. For <catalog_source_namespace>, enter the name of the catalog source namespace created for the Rhapsody Systems Engineering operator. If your catalog source namespace is not available, you can create a new namespace before you apply it.

      kubectl apply -f catalog_source.yaml -n <catalog_source_namespace> 

   2. Verify the installation by running the following command:

      kubectl get CatalogSources ibm-rse-catalog -n <catalog_source_namespace> 

      • If the installation was successful, the output is similar to this

        Name	Display	Type	Publisher	Age
        ibm-rse-catalog	IBM RSE Operator Catalog	grpc	IBM	50s

      • If the installation fails, see Fixing the issues in preparing and configuring the catalog sources by using the Kubernetes cluster for resolution.
   The YAML file is imported, and it might take some time for the catalog to connect and reach a ready state.