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 Kubernetes cluster.
1. Log in to the SWIFT dashboard, navigate to the Container Cluster menu, and click the Add button.
Refer to the screenshot below for your reference. 
2.Once you click the Add button, a Cluster Add dialog will appear. Provide the required cluster details to enable discovery. Refer to the screenshot below for your reference.
| Field Name | Field Parameter |
| 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 | Provide VCenter IP or DNS name |
| Port | By default it uses 443 |
| User Name | 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. |
| Cluster Name | Provide the Tanzu cluster name that is created in vCenter. For more information, click the ‘i’ button to view details about the Tanzu cluster name. |
| Tanzu Cluster Type | In this option there two type of tanzu cluster. You can provide as per your requirement. Supervisor managed: A Supervisor Cluster is created and managed directly by vCenter Server when Workload Management is enabled. The Supervisor Cluster leverages vSphere resources such as storage policies, networking etc. Non-Supervisor managed: Non-Supervisor-managed cluster is standalone Kubernetes clusters that are not controlled by vCenter’s Supervisor Cluster. Installed and managed independently. |
| Supervisor address | If you select Supervisor Managed, you must provide the Supervisor Address, which is the control plane endpoint of the Supervisor Cluster. If you select Non-Supervisor Managed, you need to provide the cluster key (service account token) and the port. |
| Port in Tanzu cluster config | Provide 6443 port |
| Namespace | Enter the namespace in supervisor cluster where the Tanzu cluster resides. For more information, click on 'i' button to inspect the namespace. |
| 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 used to overwrite the default kubeconfig IP with the private IP and port |
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 K8S 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 Namespace tab, you will see all the namespaces created in the cluster, including the default namespaces provided by Tanzu cluster. You can see below screenshot.
- When you go to the Kubernetes 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.
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.
How to migrate application with Passthrough sync
How to migrate applications with Stage sync
Related KB's