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 Local cluster, Ensure your local Kubernetes cluster is up and running. Also The cluster must be accessible from the SWIFT environment (API Server reachable)
2. To add Local Kubernetes cluster in SWIFT, You need to create a dedicated Service Account in the cluster and assign the appropriate permissions using a ClusterRole and ClusterRoleBinding. For detailed steps, refer to the Adding local Kubernetes cluster service account for SWIFT use section.
or
You can download the installation and prerequisite guide from the SWIFT dashboard to create credentials for the Local Kubernetes cluster. The screenshot below is for your reference.
Following are steps to discover the Local 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 guidance.
2. Once you click the Add button, the Cluster Add dialog will appear. Enter the required cluster details to proceed with the discovery. Refer to the screenshot below for guidance.
| 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. For local cluster, choose 'Native Local'. |
| IP Address / DNS Name | The reachable endpoint of the Kubernetes API server (can be the cluster’s master node IP or DNS name) used by SWIFT to connect to the local Kubernetes cluster. |
| Port | The network port on which the Kubernetes API server is exposed (default: 6443). |
| Key | The private key associated with the Service Account or client certificate, used to securely authenticate with the Kubernetes API server. Know More |
| 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. |
3. Now, click the Add button. Within a few seconds, the Local K8S cluster will be added. Refer to the screenshot below to confirm that the Local 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. Click on the cluster to expand it and see the details. Refer to the screenshot below for guidance.
- When you go to the Summary tab, you will find information about the cluster, such as its creation date, Local cluster name, API server port, Kubernetes version, and more.
- When you go to the Namespace tab, you will see all the namespaces created in the cluster, including the default namespaces provided by Local k8s cluster. Please 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 pods are running in the 'app-local-cluster' namespace.
4. 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 below 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