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 OKE cluster, you must have a cluster created in the OCI cloud and know the region where the cluster is deployed.
2. To add an Oracle Kubernetes Engine (OKE) cluster in SWIFT, you need Oracle Cloud Infrastructure (OCI) credentials and configuration details. These credentials allow SWIFT to authenticate and connect to your OCI tenancy for cluster discovery. We need to provide the UserID, Compartment ID, tenancy ID and fingerprint to discover the OKE cluster. For that please refer to the Pre-requisite Guide (pages 14–31) provided below.
https://rackware.freshdesk.com/a/solutions/articles/5000888958?lang=en
Following are steps to discover the OKE 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. 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. In this case it is Oracle OCI. |
| Cluster Name in OCI Cloud | Enter the OKE cluster name that you created in oracle cloud. |
| User ID | Unique identifier of the OCI IAM user used for authentication. |
| Compartment ID | Identifier of the OCI compartment where the OKE cluster resides |
| Tenant ID | Unique identifier of your OCI tenancy (root account). |
| API Key Fingerprint | API key fingerprint associated with the OCI user. |
| Realm Type | The Oracle Cloud realm that represents your geographic region. |
| Region | The specific OCI region where your OKE cluster is deployed (e.g., us-ashburn-1). |
| Private Key file | The private key (.pem) file that matches the public key uploaded to OCI. |
| 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 OKE cluster will be added. Please check below screenshot that OKE has been 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. 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, OCI 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 OKE. 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' 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. 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: https://rackware.freshdesk.com/a/solutions/articles/5000891530?lang=en
Stage sync: https://rackware.freshdesk.com/a/solutions/articles/5000891530?lang=en
Related KB's
How to create DR Policy : https://rackware.freshdesk.com/a/solutions/articles/5000890832?lang=en
DR policy for stage1+2 sync: https://rackware.freshdesk.com/a/solutions/articles/5000890839?lang=en