Installing the CAM Operator on an OpenShift Container Platform 3 source cluster

You can install the CAM Operator manually on an OpenShift Container Platform 3.7 (or later) source cluster, which does not support OLM.

The CAM Operator installs Restic and Velero.

Prerequisites
  • You must have podman installed.

  • Your OpenShift Container Platform 3 cluster must be configured to pull images from registry.redhat.io.

    The registry.redhat.io registry does not allow unauthenticated access. You must have registry.redhat.io configured with credentials in order to authenticate. See this Red Hat Solution for instructions to configure this registry for OpenShift Container Platform 3.7, 3.9, or 3.10 clusters. Be sure to distribute the credentials to all nodes in your cluster.

If your system is configured for rootless Podman containers, sudo is not required for this procedure.

Procedure
  1. Log in to the Red Hat Container Registry with your Red Hat Customer Portal credentials:

    $ sudo podman login registry.redhat.io
  2. Download the operator.yml file:

    $ sudo podman cp $(sudo podman create registry.redhat.io/rhcam-1-1/openshift-migration-rhel7-operator:v1.1):/operator.yml ./
  3. Download the controller-3.yml file:

    $ sudo podman cp $(sudo podman create registry.redhat.io/rhcam-1-1/openshift-migration-rhel7-operator:v1.1 ):/controller-3.yml ./
  4. Create the CAM Operator CR object:

    $ oc create -f operator.yml
    namespace/openshift-migration created
    rolebinding.rbac.authorization.k8s.io/system:deployers created
    serviceaccount/migration-operator created
    customresourcedefinition.apiextensions.k8s.io/migrationcontrollers.migration.openshift.io created
    role.rbac.authorization.k8s.io/migration-operator created
    rolebinding.rbac.authorization.k8s.io/migration-operator created
    clusterrolebinding.rbac.authorization.k8s.io/migration-operator created
    deployment.apps/migration-operator created
    Error from server (AlreadyExists): error when creating "./operator.yml": rolebindings.rbac.authorization.k8s.io "system:image-builders" already exists (1)
    Error from server (AlreadyExists): error when creating "./operator.yml": rolebindings.rbac.authorization.k8s.io "system:image-pullers" already exists (1)
    1 You can ignore the Error from server (AlreadyExists) messages. They are caused by the CAM Operator creating resources for earlier versions of OpenShift Container Platform 3 that are provided in later releases.
  5. Create the Migration controller CR object:

    $ oc create -f controller-3.yml
  6. Verify that the Velero and Restic Pods are running:

    $ oc get pods -n openshift-migration

Installing the CAM Operator on an OpenShift Container Platform 4.3 target cluster

You can install the CAM Operator on an OpenShift Container Platform 4.3 target cluster with OLM.

The CAM Operator installs the following on the target cluster:

  • Migration controller CR

  • CAM web console

  • Restic

  • Velero

Procedure
  1. In the OpenShift Container Platform web console, click AdministrationNamespaces.

  2. On the Namespaces page:

    1. Click Create Namespace.

    2. Enter openshift-migration in the Name field and click Create.

  3. Click OperatorsOperatorHub.

  4. On the OperatorHub page:

    1. Scroll or type a keyword into the Filter by keyword field (in this case, Migration) to find the Cluster Application Migration Operator.

    2. Select the Cluster Application Migration Operator and click Install.

  5. On the Create Operator Subscription page:

    1. Select the openshift-migration namespace if it is not already selected.

    2. Select an Automatic or Manual approval strategy.

    3. Click Subscribe.

  6. Click OperatorsInstalled Operators.

    The Cluster Application Migration Operator is listed in the openshift-migration project with the status InstallSucceeded.

  7. On the Installed Operators page:

    1. Under Provided APIs, click View 12 more…​.

    2. Click Create NewMigrationController.

    3. Click Create.

  8. Click WorkloadsPods to verify that the Restic and Velero Pods are running.

  9. Click WorkloadsPods to verify that the Controller Manager, Migration UI, Restic, and Velero Pods are running.