1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/migration-installing-migration-operator-manually.adoc
2019-10-30 09:01:25 +02:00

71 lines
1.9 KiB
Plaintext

// Module included in the following assemblies:
//
// migration/migrating_openshift_3_to_4/migrating-openshift-3-to-4.adoc
[id="installing-migration-operator-manually_{context}"]
= Installing the CAM Operator manually on {product-title} 3
You can install the CAM Operator manually on an {product-title} 3 source cluster, which does not support OLM.
// [NOTE]
// ====
// You can install the CAM Operator manually on an {product-title} 4 cluster, but it is normally installed with OLM.
// ====
.Prerequisites
* You must have `podman` installed.
.Procedure
. Download the `operator.yml` file:
+
----
$ podman cp $(podman create registry.redhat.io/rhcam-1-0/openshift-migration-rhel7-operator:v1.0 ):/operator.yml ./
----
. Download the `controller-3.yml` file:
//
// * {product-title} 3:
+
----
podman cp $(podman create registry.redhat.io/rhcam-1-0/openshift-migration-rhel7-operator:v1.0 ):/controller-3.yml ./
----
//
// * {product-title} 4:
// +
// ----
// $ podman cp $(podman create registry.redhat.io/rhcam-1-0/openshift-migration-rhel7-operator:v1.0 ):/controller-4.yml ./
// ----
// +
// The `controller-4.yml` file installs the Migration controller CR and CAM web console on the {product-title} 4 cluster by default. If you do not want to install them on this cluster, update the values of the following parameters:
// +
// [source,yaml]
// ----
// migration_controller: false
// migration_ui: false
// ----
. Create the CAM Operator CR object:
+
----
$ oc create -f operator.yml
----
. Create the Migration controller CR object:
//
// * {product-title} 3:
+
----
$ oc create -f controller-3.yml
----
//
// * {product-title} 4:
// +
// ----
// $ oc create -f controller-4.yml
// ----
. Use the `oc get pods` command to verify that Velero is running.
// +
// If you installed the Migration controller and CAM web console on the cluster, verify that the migration controller and migration UI are also running.