For any migration or disaster recovery (DR) activity, the first step is to discover the cluster in SWIFT. Discovery allows SWIFT to identify and register the cluster along with its associated resources such as namespaces, workloads, and other objects. Only after the cluster is successfully discovered, you can proceed with operations like syncing applications, or performing the actual migration or failover tasks.
Pre-requisite:
1. . To discover the Azure OpenShift container platform cluster, you must have a cluster created in the OKD cloud and know the region where the cluster is deployed.
2. To adding service account token. Please refer Adding OpenShift cluster service account for SWIFT section.
Following are steps to discover the IBM OpenShift origin (OKD) cluster.
1. We need to login to the ‘SWIFT’ dashboard and navigate to the ‘container cluster’ menu and click on ‘Add’ button. Please check below screenshot for your reference.
2. Once you click on 'Add ' button. It will appear Cluster Add modal/dialog. There you need to provide cluster details to be discovered. Please check below screenshot for your reference .
| Field Name | Field Description |
| Platform type | Select the platform where your cluster is running |
| Friendly name | You need to enter a friendly name according to your cluster or project |
| Cloud Type | Choose the ‘cloud type’ from the dropdown as SWIFT supports various clouds |
| Service Account toekn | In an OKD cluster, a service account token is a secret token linked to a service account, used for secure, automated access to the Kubernetes/OKD API (f |
| Port | OKD cluster API is accessed on port 6443 |
| IP Address/DNS name | This DNS resolves to the cluster’s public or private IP, depending on your setup. |
| API Key | In OKD, an API key is essentially a service account token or user token used to authenticate to the Kubernetes/OKD API |
| TRAIPOD Config & Cluster Private IP Config | This is an optional input. They can be configured for each sync, and the values input for the sync will override the defaults set for the cluster. For more info you can look TRAIPOD KB article. To more know about Traipod Config section, Please follow below KB Article. https://rackware.freshdesk.com/a/solutions/articles/5000890139?lang=en |
| Cluster private IP config | Normally, the IP address or hostname mentioned in the kubeconfig file is used to discover the cluster. However, if you want to set up a private IP or hostname to access the cluster, and the public IP mentioned in the kubeconfig is not used, this setting can be used to overwrite the default kubeconfig IP with the private IP and port. |
3. Now just click on 'Add' button and within few seconds, the IBM OpenShift origin cluster will be added. Please check below screenshot that IBM OpenShift origin cluster has been discovered in SWIFT.
Note: These steps are based on IBM OpenShift origin cluster discovery in IBM Cloud. They will be updated with screenshots and OKD-specific details once the clusters are ready.
4. Once the cluster is discovered, you can view all information about the cluster and its metadata. Simply expand the cluster by clicking on it, and you will see the details. Please refer to the screenshot below.
- When you go to the Summary tab, you will find information about the cluster, such as its creation date, azure openshift cluster name, API server port, OpenShift version, and more.
- When you go to the OpenShift Objects tab, you can view the objects running in your namespace. Simply select the object type from the Object Type tab and choose the namespace from the dropdown. This will display the objects running in that namespace on the cluster. In the screenshot below, you can see that two pods are running in the 'openshift-dns' namespace.
5. Once you discovered the cluster, you will get more operations of following options. You can run other operation as below for the selected discovered cluster.
- Re-Discover : This option allows you to re-discover the cluster. If you have added new namespaces or applications to the cloud cluster and want them to be reflected in the SWIFT portal, you can re-discover the cluster. Please refer to the link below for detailed steps on how to re-discover a cluster.
<link>
- Configure : Use this option if you want to modify the cluster configuration. Please check KB Article on 'Configure the cluster'
https://rackware.freshdesk.com/a/solutions/articles/5000897684?lang=en
- Delete : Use this option to delete the cluster. However, ensure that no DR Policy is attached to the cluster; otherwise, the cluster cannot be deleted and the Delete option will be disabled. It will delete from SWIFT dashboard only not from cloud.
What next:
- Now that the clusters are discovered, you may want to set up a Migration or Disaster Recovery (DR) job. Then follow below KB links.
Passthrough sync:
Stage sync:
Related KB's
How to create DR Policy :
DR policy for stage1+2 sync: