You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: migration/migrating_3_4/deploying-cam-3-4.adoc
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,13 +15,18 @@ Optional: You can configure the {mtc-full} Operator to install the {mtc-short} l
15
15
16
16
In a restricted environment, you can install the {mtc-full} Operator from a local mirror registry.
17
17
18
-
After you have installed the {mtc-full} Operator on your clusters, you can launch the {mtc-short} web console.
18
+
After you have installed the {mtc-full} Operator on your clusters, you can launch the {mtc-short} console.
19
19
20
20
[id='installing-cam-operator_{context}']
21
21
== Installing the {mtc-full} Operator
22
22
23
23
You can install the {mtc-full} Operator with the Operator Lifecycle Manager (OLM) on an {product-title} {product-version} target cluster and manually on an {product-title} 3 source cluster.
24
24
25
+
[IMPORTANT]
26
+
====
27
+
You must ensure that the same Operator version is installed on the source and target clusters.
= Installing the {mtc-full}Operator on an {product-title} 3 source cluster
7
+
= Installing the {mtc-full} on an {product-title} 3 source cluster
7
8
8
-
You can install the {mtc-full} ({mtc-short}) Operator manually on an {product-title} 3 source cluster.
9
+
You can install the {mtc-full} ({mtc-short}) manually on an {product-title} 3 source cluster.
9
10
endif::[]
10
11
ifdef::disconnected-3-4[]
11
-
= Installing the {mtc-full}Operator on an {product-title} 3 source cluster in a restricted environment
12
+
= Installing the {mtc-full} on an {product-title} 3 source cluster in a restricted environment
12
13
13
14
You can create a manifest file based on the {mtc-full} ({mtc-short}) Operator image and edit the manifest to point to your local image registry. Then, you can use the local image to create the {mtc-full} Operator on an {product-title} 3 source cluster.
14
15
endif::[]
15
16
16
17
[IMPORTANT]
17
18
====
18
-
You must install the same {mtc-short} version on the {product-title} 3 and 4 clusters. The {mtc-full} Operator on the {product-title} 4 cluster is updated automatically by the Operator Lifecycle Manager.
19
+
You must install the same {mtc-short} version on the {product-title} 3 and 4 clusters. The {mtc-full} Operator on the {product-title} 4 cluster is updated automatically by Operator Lifecycle Manager.
19
20
20
21
To ensure that you have the latest version on the {product-title} 3 cluster, download the `operator.yml` and `controller-3.yml` files when you are ready to create and run the migration plan.
21
22
====
22
23
23
24
.Prerequisites
24
25
25
26
* Access to `registry.redhat.io`
27
+
* Podman installed
26
28
ifdef::migrating-3-4[]
27
29
* {product-title} 3 cluster configured to pull images from `registry.redhat.io`
<1> You can ignore `Error from server (AlreadyExists)` messages. They are caused by the {mtc-full} Operator creating resources for earlier versions of {product-title} 3 that are provided in later releases.
You can install the {mtc-full} ({mtc-short}) Operator on an {product-title} 4 source cluster with the Operator Lifecycle Manager (OLM).
28
+
You can install the {mtc-full} ({mtc-short}) on an {product-title} 4 source cluster by using Operator Lifecycle Manager (OLM) to install the {mtc-full} Operator.
You can install the {mtc-full} ({mtc-short}) Operator on an {product-title}{product-version} target cluster with the Operator Lifecycle Manager (OLM).
32
+
You can install the {mtc-full} ({mtc-short}) on an {product-title}{product-version} target cluster by using Operator Lifecycle Manager (OLM) to install the {mtc-full} Operator.
33
33
34
-
The {mtc-full} Operator installs the {mtc-short} on the target cluster by default.
34
+
{mtc-short} is installed on the target cluster by default.
. Use the *Filter by keyword* field to find the *{mtc-full} Operator*.
53
53
. Select the *{mtc-full} Operator* and click *Install*.
54
-
. On the *Install Operator* page, click *Install*.
54
+
ifdef::migrating-3-4[]
55
+
+
56
+
[NOTE]
57
+
====
58
+
Do not change the subscription approval option to *Automatic*. The {mtc-full} Operator version must be the same on the source and the target clusters.
59
+
====
60
+
endif::[]
61
+
62
+
ifdef::target-4-2-4,source-4-2-4,target-4-1-4[]
63
+
. In the *Subscription* tab, change the *Approval* option to *Automatic*.
64
+
endif::[]
65
+
. Click *Install*.
55
66
+
56
67
On the *Installed Operators* page, the *{mtc-full} Operator* appears in the *openshift-migration* project with the status *Succeeded*.
57
68
58
69
. Click *{mtc-full} Operator*.
59
70
. Under *Provided APIs*, locate the *Migration Controller* tile, and click *Create Instance*.
60
71
61
72
ifdef::source-4-1-4[]
62
-
. Set the `migration_controller` and `migration_ui` parameters to `false`and add the `deprecated_cors_configuration: true` parameter to the `spec` stanza:
73
+
. Update the `migration_controller` and `migration_ui` parameters and add the `deprecated_cors_configuration` parameter to the manifest:
63
74
+
64
75
[source,yaml]
65
76
----
66
77
spec:
67
-
...
78
+
...
68
79
migration_controller: false
69
80
migration_ui: false
70
-
...
81
+
...
71
82
deprecated_cors_configuration: true
72
83
----
73
84
endif::[]
74
85
ifdef::source-4-2-4[]
75
-
. Set the `migration_controller` and `migration_ui` parameters to `false`in the `spec` stanza:
86
+
. Update the `migration_controller` and `migration_ui` parameters in the manifest:
76
87
+
77
88
[source,yaml]
78
89
----
79
90
spec:
80
-
...
91
+
...
81
92
migration_controller: false
82
93
migration_ui: false
83
-
...
84
94
----
85
95
endif::[]
86
96
87
97
. Click *Create*.
88
-
ifdef::source-4-1-4,source-4-2-4[]
89
-
. Click *Workloads*->*Pods* to verify that the `Restic` and `Velero` pods are running.
Copy file name to clipboardExpand all lines: modules/migration-running-migration-plan-cam.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ $ oc adm prune images
29
29
----
30
30
31
31
. Log in to the {mtc-short} web console and click *Migration plans*.
32
-
. Click the *Options* menu {kebab} beside a migration plan and select *Stage* to copy data from the source cluster to the target cluster without stopping the application.
32
+
. Click the *Options* menu {kebab} next to a migration plan and select *Stage* to copy data from the source cluster to the target cluster without stopping the application.
33
33
+
34
34
You can run *Stage* multiple times to reduce the actual migration time.
= Upgrading the {mtc-full}Operator on an {product-title} 3 cluster
6
+
= Upgrading the {mtc-full} on an {product-title} 3 cluster
7
7
8
8
You can upgrade {mtc-full} ({mtc-short}) on an {product-title} 3 cluster by downloading the latest `operator.yml` file and replacing the existing {mtc-full} Operator.
9
9
10
-
[NOTE]
11
-
====
12
-
If you remove and recreate the namespace, you must update the cluster service account token in the {mtc-short} web console.
. If you have already added your {product-title} 3 source cluster to the {mtc-short} console, you must update the service account token because the upgrade deletes and restores the `openshift-migration` namespace:
88
+
89
+
.. Obtain the service account token:
90
+
+
91
+
[source,terminal]
92
+
----
93
+
$ oc sa get-token migration-controller -n openshift-migration
94
+
----
95
+
96
+
.. In the {mtc-short} console, click *Clusters*, click the Options menu {kebab} next to the source cluster, and select *Edit*.
97
+
98
+
.. Enter the new service account token in the *Service account token* field, click *Update cluster*, and then click *Close*.
= Upgrading the {mtc-full}Operator on an {product-title} 4 cluster
7
+
= Upgrading the {mtc-full} on an {product-title} 4 cluster
8
8
9
-
ifeval::["{mtc-version}" > "1.3"]
10
-
You can upgrade the {mtc-full} ({mtc-short}) Operator on an {product-title} 4 cluster with the Operator Lifecycle Manager.
9
+
You can upgrade the {mtc-full} ({mtc-short}) on an {product-title} 4 cluster using the {product-title} console.
11
10
11
+
ifdef::migrating-4-1-4,migrating-4-2-4[]
12
12
If you selected the *Automatic* approval option when you installed the {mtc-full} Operator, the Operator is updated automatically.
13
13
14
14
The following procedure enables you to change the *Manual* approval option to *Automatic* or to change the release channel.
15
+
endif::[]
15
16
16
17
.Procedure
17
18
18
-
. In the {product-title} console, navigate to *Operators* > *Installed Operators*.
19
+
. In the {product-title} console, navigate to *Operators* -> *Installed Operators*.
19
20
. Click *{mtc-full} Operator*.
21
+
ifdef::migrating-4-1-4,migrating-4-2-4[]
20
22
. In the *Subscription* tab, change the *Approval* option to *Automatic*.
21
23
. Optional: Edit the *Channel*.
22
24
+
23
25
Updating the subscription deploys the updated {mtc-full} Operator and updates the {mtc-short} components.
24
26
endif::[]
25
-
ifeval::["{mtc-version}" <= "1.3"]
26
-
You can upgrade to {mtc-full} ({mtc-short}) {mtc-version} on an {product-title} 4 cluster by deleting the `MigrationController` custom resource (CR), uninstalling the CAM Operator, and then installing the {mtc-full} Operator.
27
-
28
-
.Procedure
29
27
30
-
. Delete the `MigrationController` CR:
28
+
. Under *Provided APIs*, locate the *Migration Controller* tile, and click *Create Instance*.
29
+
ifdef::migrating-4-1-4[]
30
+
. If you are upgrading {mtc-short} on a 4.1 _source_ cluster, update the `migration_controller` and `migration_ui` parameters and add the `deprecated_cors_configuration` parameter to the `migration_controller` manifest:
You do not need to update the manifest of the target cluster.
44
+
====
45
+
endif::[]
36
46
37
-
. In the {product-title} console, navigate to *Operators* > *Installed Operators*.
38
-
. Click *CAM Operator*.
39
-
. On the right side of the *Operator Details* page, select *Uninstall Operator* from the *Actions* list.
40
-
. Select *Uninstall*. This Operator stops running and no longer receives updates.
41
-
. Navigate to *Operators* -> *OperatorHub*.
42
-
. Use the *Filter by keyword* field to find the *{mtc-full} Operator*.
43
-
. Select the *{mtc-full} Operator* and click *Install*.
44
-
. On the *Install Operator* page, click *Install*.
47
+
ifdef::migrating-4-2-4[]
48
+
. If you are upgrading {mtc-short} on a 4.2 _source_ cluster, update the `migration_controller` and `migration_ui` parameters in the `migration_controller` manifest:
45
49
+
46
-
On the *Installed Operators* page, verify that the *{mtc-full} Operator* appears in the *openshift-migration* project with the status *Succeeded*.
50
+
[source,yaml]
51
+
----
52
+
spec:
53
+
...
54
+
migration_controller: false
55
+
migration_ui: false
56
+
----
57
+
+
58
+
[NOTE]
59
+
====
60
+
You do not need to update the manifest of the target cluster.
61
+
====
47
62
endif::[]
63
+
64
+
. Click *Create*.
65
+
. Click *Workloads* -> *Pods* to verify that the {mtc-short} pods are running.
0 commit comments