Migrating from Docker to the IBM Container Registry

1. Enter the following command to edit the CatalogSource:

   oc edit catalogsource ibm-operator-catalog -n openshift-marketplace
   

2. Navigate to the spec section of the YAML file, then update the image reference to be icr.io/cpopen/ibm-operator-catalog:latest.

   spec:
     displayName: IBM Operator Catalog
     image: icr.io/cpopen/ibm-operator-catalog:latest
     publisher: IBM
     sourceType: grpc
     updateStrategy:
       registryPoll:
         interval: 45m
   

3. Save your edited CatalogSource YAML file. If the file is successfully edited and saved, the following message appears:

   catalogsource.operators.coreos.com/ibm-operator-catalog edited
   

4. Restart the ibm-operator-catalog pod. Navigate to your openshift-marketplace project and enter the following command to ensure that the pod restarted:

   oc get catalogsource ibm-operator-catalog -n openshift-marketplace
   

Important: Make sure you have the role of Administrator before editing the CatalogSource.

1. Click Home > Explore, then enter catalogsource as the filter value to locate your CatalogSource YAML file.

   

2. Click CatalogSource, then click Instances and search for ibm-operator-catalog.

3. Click the options menu (three vertical dots) and select Edit CatalogSource.

   

4. Scroll to the spec section of the YAML file and replace docker.io/ibmcom with icr.io/cpopen, then click Save.

   

5. Verify that CatalogSource has been implemented:

   1. From the navigation bar, click Workloads > Pods.
   2. Select openshift-marketplace in the Project drop-down menu.
   3. Enter ibm-operator-catalog in the search bar.

   4. Click ibm-operator-catalog link, then scroll to the Conditions to ensure that the CatalogSource has been updated.

      

You can also upgrade the IBM Operator Helm chart from 1.0.0 to 1.1.0. This upgrade automatically changes the image reference from docker.io/ibmcom/ibm-operator-catalog:latest to icr.io/cpopen/ibm-operator-catalog:latest.

1. Log in to your console instance and select the Developer view.

   

2. Click Add, then click From Catalog.

   

3. Enter the project and namespace where you want to install the Helm release.

   

4. Select Helm Charts and enter operator in the search bar.

   

5. Click the Ibm Operator Catalog tile, then click Install Helm Chart.

6. Accept the license by entering true in the license field.

   

7. Click Install.

Note: The 1.1.0 version of the Helm chart gives you the option to Deploy Mirror Config. If that value is toggled to true, it will also upgrade the ImageContentSourcePolicy (the next step and second consideration of your migration from Docker to the IBM Container Registry).

The Red Hat OpenShift Container Platform ImageContentSourcePolicy resource updates the image pull process, allowing cluster level configuration of registry mirrors. After the mirror is added, for every image pull attempted by using a digest from the source registry (docker.io/ibmcom), the node attempts to pull from the mirror registry (icr.io/cpopen). If the digest is not found, the cluster reverts to the source registry.

Important: An ImageContentSourcePolicy is implemented by changing the configuration of the cluster nodes. For Red Hat OpenShift Container Platform 4.6 and earlier, all of the worker nodes restart one at a time after implementation. From Red Hat OpenShift Container Platform 4.7 and later, worker nodes are drained, one at a time, without restarting the node. During this process, pods are rescheduled on to alternative nodes. You must ensure that your cluster has sufficient capacity.

You can create or update an ImageContentSourcePolicy by either of the following methods:

• Creating a new ImageContentSourcePolicy
• Updating an ImageContentSourcePolicy