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. SWIFT can be located anywhere, but it must have connectivity to the cluster and vice versa.
2. The user should have permission for the datastore, specifically “Low Level File Operations.”
Following are steps to discover the VMWare OpenShift cluster.
1. 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 display Cluster Add modal/dialog. There you need to provide cluster details to be discovered. You can check below screenshot for your reference.
| Field Parameter | 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. |
| IP Address / DNS Name in vCenter Config | Provide VCenter IP or DNS name |
| Port | By default it uses 6443 |
| Username | Please provide the username you are using to log in to vCenter. |
| Password | You can provide directly or upload the file which you are using to login to vCenter. |
| Service account token (OpenShift Cluster Config) | A Service Account Token is a secure credential used to authenticate applications or tools to the VMware OpenShift cluster API without using a personal user account. |
| Port (OpenShift Cluster Config) | Be default it uses6443 |
| IP Address / DNS name | IP Address / DNS Name is the network endpoint of the OpenShift cluster API server, used to connect and manage the cluster. |
| TRAIPOD 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. traipod-config |
| 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 use. |
3. Now, click the Add button. Within a few seconds, the VMWare Kubernetes cluster will be added. Refer to the screenshot below to confirm that the VMWare OpenShift cluster has been successfully discovered in SWIFT.
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. You can refer to the screenshot below .
- When you go to the Summary tab, you will find information about the cluster, such as its creation date, cluster name, API server port, Kubernetes version, and more. It will display the basic details of cluster.
- 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 services are running in the 'default' namespace.
5. Once the cluster is discovered, you will have access to additional operations. You can perform the following actions on the selected 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.
- Configure : Use this option if you want to modify the cluster configuration. Please check KB Article on 'Configure the cluster'
- 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.