mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-07 00:48:01 +01:00
69 lines
3.2 KiB
Plaintext
69 lines
3.2 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
|
|
// * migration_toolkit_for_containers/migrating-applications-with-mtc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="migration-adding-cluster-to-cam_{context}"]
|
|
= Adding a cluster to the {mtc-short} web console
|
|
|
|
You can add a cluster to the {mtc-full} ({mtc-short}) web console.
|
|
|
|
.Prerequisites
|
|
|
|
* If you are using Azure snapshots to copy data:
|
|
** You must specify the Azure resource group name for the cluster.
|
|
** The clusters must be in the same Azure resource group.
|
|
** The clusters must be in the same geographic location.
|
|
* If you are using direct image migration, you must expose a route to the image registry of the source cluster.
|
|
|
|
.Procedure
|
|
|
|
. Log in to the cluster.
|
|
. Obtain the `migration-controller` service account token:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc sa get-token migration-controller -n openshift-migration
|
|
----
|
|
+
|
|
.Example output
|
|
+
|
|
[source,terminal]
|
|
----
|
|
eyJhbGciOiJSUzI1NiIsImtpZCI6IiJ9.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJtaWciLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlY3JldC5uYW1lIjoibWlnLXRva2VuLWs4dDJyIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQubmFtZSI6Im1pZyIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50LnVpZCI6ImE1YjFiYWMwLWMxYmYtMTFlOS05Y2NiLTAyOWRmODYwYjMwOCIsInN1YiI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDptaWc6bWlnIn0.xqeeAINK7UXpdRqAtOj70qhBJPeMwmgLomV9iFxr5RoqUgKchZRG2J2rkqmPm6vr7K-cm7ibD1IBpdQJCcVDuoHYsFgV4mp9vgOfn9osSDp2TGikwNz4Az95e81xnjVUmzh-NjDsEpw71DH92iHV_xt2sTwtzftS49LpPW2LjrV0evtNBP_t_RfskdArt5VSv25eORl7zScqfe1CiMkcVbf2UqACQjo3LbkpfN26HAioO2oH0ECPiRzT0Xyh-KwFutJLS9Xgghyw-LD9kPKcE_xbbJ9Y4Rqajh7WdPYuB0Jd9DPVrslmzK-F6cgHHYoZEv0SvLQi-PO0rpDrcjOEQQ
|
|
----
|
|
|
|
. In the {mtc-short} web console, click *Clusters*.
|
|
. Click *Add cluster*.
|
|
. Fill in the following fields:
|
|
|
|
* *Cluster name*: The cluster name can contain lower-case letters (`a-z`) and numbers (`0-9`). It must not contain spaces or international characters.
|
|
* *URL*: Specify the API server URL, for example, `\https://<www.example.com>:8443`.
|
|
* *Service account token*: Paste the `migration-controller` service account token.
|
|
* *Exposed route host to image registry*: If you are using direct image migration, specify the exposed route to the image registry of the source cluster.
|
|
+
|
|
To create the route, run the following command:
|
|
+
|
|
** For {product-title} 3:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc create route passthrough --service=docker-registry --port=5000 -n default
|
|
----
|
|
** For {product-title} 4:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc create route passthrough --service=image-registry --port=5000 -n openshift-image-registry
|
|
----
|
|
|
|
* *Azure cluster*: You must select this option if you use Azure snapshots to copy your data.
|
|
* *Azure resource group*: This field is displayed if *Azure cluster* is selected. Specify the Azure resource group.
|
|
* *Require SSL verification*: Optional: Select this option to verify SSL connections to the cluster.
|
|
* *CA bundle file*: This field is displayed if *Require SSL verification* is selected. If you created a custom CA certificate bundle file for self-signed certificates, click *Browse*, select the CA bundle file, and upload it.
|
|
|
|
. Click *Add cluster*.
|
|
+
|
|
The cluster appears in the *Clusters* list.
|