• How to discover the cloud k8s cluster.


  • Discover the AWS cluster with SWIFT
  1. First, we need to login to the SWIFT dashboard and navigate to the ‘container cluster’ menu and click on Add button.



  1. Once you click on the Add button you will appear a screen below and select the ‘cloud type’ from the dropdown menu.



  1. Friendly name: You need to enter a friendly name according to your cluster or project.
  2. Cloud Type: Choose the cloud type from the dropdown as SWIFT supports various K8S clouds.
  3. Cluster Name: Put the EKS cluster name.
  4. Access Key: Provide the Access key of your aws account.
  5. Region: Select the region from dropdown where EKS cluster is present.
  6. Secret Key: Provide your aws secret key.
  7. 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.
  8.  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.            
  9. If you click on Advanced Option tab you will get as below.



  • Ceph Dashboard Secret: If cluster uses ceph storage service, provide K8S secret which has caph credential in it.  On k8s cluster , deploy the ceph dashboard and expose it using either ‘Nodeport’ or ‘LoadBalancer’. Please use this link to create a ceph dashboard.
  • Once the ceph dashboard is deployed, create a secret on K8S with following command.
    1. $ kubectl create secret generic / --from-literal=dashboard-username= / --from-literal=dashboard-password= / --from-literal=dashboard-address= / [--from-literal=dashboard-port=]
    2. Note: The dashboard-port is optional if the ceph dashboard is exposed using k8s ingress object.
  • TRAIPOD Configuration: In the above snippet you can see the CPU and Memory request limit, in that we can restrict TraiPod resources.


Then you can click on the ‘Add’ button to discover the EKS cluster. It will discover in 3-4 seconds.




 

  • Discover the GCP/GKE cluster with SWIFT
    1. We need to login to the ‘SWIFT’ dashboard and navigate to the ‘container cluster’ menu and click on ‘Add’ button.
    2. Once you click on the Add button you will appear a screen below and select the ‘cloud type’ from the dropdown menu.



  1. Friendly name: You need to enter a friendly name according to your cluster or project.
  2. Cloud Type: Choose the ‘cloud type’ from the dropdown as SWIFT supports various K8S clouds.
  3. Cluster Name: Put the GKE cluster name.
  4. Region: Choose the region from the provided list that matches the region of your GKE cluster.
  5. Private key File: Click on the button to browse your local system and select the private key file (e.g., service-account-key.json). 
  6. TRAIPOD Config & Cluster Private IP Config: You can refer to the AWS cluster discovery section. We have explained it very well there, as this option is very similar across all clouds.
  7. Advanced Options: Also refer to the AWS cluster discovery section as this is also similar across all k8s clouds.
  8. Then you can click on the ‘Add’ button to discover the GKE cluster. It will be discovered in 3-4 seconds.



  • Discover the Azure/AKS cluster with SWIFT
    1. We need to login to the ‘SWIFT’ dashboard and navigate to the ‘container cluster’ menu and click on ‘Add’ button.
    2. Once you click on the Add button you will appear a screen below and select the ‘cloud type’ from the dropdown menu.


  1. Friendly name: You need to enter a friendly name according to your cluster or project.
  2. Cloud Type: Choose the ‘cloud type’ from the dropdown as SWIFT supports various K8S clouds.
  3. Cluster Name: Put the AKS cluster name.
  4. Subscription ID: Put the Subscription ID. This is a unique identifier for your subscription. 
  5. Tenant ID: Put the Tenant ID as this is unique identifier for your Azure AD instance.
  6. Resource group: Provide resource group as this is a logical container that holds related resources for an Azure solution. It enables you to manage and organize resources such as virtual machines, storage accounts, and virtual networks.
  7. Client ID: Put the client ID in this section from azure portal. This is a password-like string that is generated when you register an application in Azure AD.
  8. TraiPOD Config, Cluster Private IP config and Advanced option: This is similar across all K8S clouds, so please refer to the AWS discovery section.
  9. Then you can click on the ‘Add’ button to discover the ASK cluster. It will be discovered in 3-4 seconds.




  • Discover the OCI/OKE cluster with SWIFT
    1. We need to login to the ‘SWIFT’ dashboard and navigate to the ‘container cluster’ menu and click on ‘Add’ button.
    2. Once you click on the Add button you will appear a screen below and select the ‘cloud type’ from the dropdown menu.




  1. Friendly name: You need to enter a friendly name according to your cluster or project.
  2. Cloud Type: Choose the ‘cloud type’ from the dropdown as SWIFT supports various K8S clouds.
  3. Cluster Name: Put the OKE cluster name.
  4. User ID: Provide User ID that is unique for the user in OCI, it is assigned when user is created in OCI.
  5. Compartment ID: Put the compartment ID which is logical partitions within an OCI tenancy that help organize and isolate resources.
  6. Tenant ID: Put the tenant ID. The Tenant ID in OCI refers to the root compartment OCID of your OCI tenancy. It is also known as the root compartment.
  7. API key’s fingerprint: Provide the ‘API key’. This API key is being used for authentication and authorization when interacting with OCI resources via APIs. It consists of public and private key pairs.
  8. Region: Choose the correct ‘region’ from the dropdown where OCI resources are hosted.
  9. Private key file: Attach a private key file for authentication purposes, such as generating and managing API signing keys or SSH keys.
  10.  TraiPOD Config, Cluster Private IP config and Advanced option: This is similar across all K8S clouds, so please refer to the AWS discovery section.
  11. Then you can click on the ‘Add’ button to discover the OKE cluster. It will be discovered in 3-4 seconds 




  • Discover the IBM/AKS cluster with SWIFT
    1. We need to login to the ‘SWIFT’ dashboard and navigate to the ‘container cluster’ menu and click on ‘Add’ button.
    2. Once you click on the Add button you will appear a screen below and select the ‘cloud type’ as a ‘IBM Cloud’ from the dropdown menu.



  1. Friendly name: You need to enter a friendly name according to your cluster or project.
  2. Cloud Type: Choose the ‘cloud type’ from the dropdown as SWIFT supports various K8S clouds.
  3. Cluster Name: Put the IKS cluster name.
  4. API Key: Input or upload api key file in this section to authenticate the identity of the user or application making the API call.
  5. TraiPOD Config, Cluster Private IP config and Advanced option: This is similar across all K8S clouds, so please refer to the AWS discovery section.
  6. Click on ‘Add’ and IBM K8S cluster will be discovered within 3-4 seconds.



Discover the LKE (Linode Kubernetes Engine) cluster with SWIFT


  1. Linode Kubernetes Engine (LKE) is a managed Kubernetes service provided by Linode, a cloud hosting provider. LKE allows users to deploy, manage, and scale containerized applications using Kubernetes on Linode's infrastructure.
  2. We need to login to the ‘SWIFT’ dashboard and navigate to the ‘container cluster’ menu and click on ‘Add’ button.
  3. Once you click on the Add button you will appear a screen below and select the ‘cloud type’ as a ‘Linode Cloud’ from the dropdown menu.




  1. Friendly name: You need to enter a friendly name according to your cluster or project.
  2. Cloud Type: Choose the ‘cloud type’ from the dropdown as SWIFT supports various K8S clouds.
  3. Cluster Name: Put the LKE cluster name where you created the K8S cluster.
  4. Region: Provide the region where the LKE cluster is deployed.
  5. Access Token: You need to log in to the ‘LKE cloud’ and navigate to the ‘API tokens’ section. Then, click on the "Create a Personal Access Token" button. Set the permissions for the token; for managing LKE clusters, you typically need read-write access. Lastly, click on the "Create Token" button. Make sure to copy it and store it securely, as you will need it when discovering the LKE cluster.
  6. TraiPOD Config, Cluster Private IP config and Advanced option: This is similar across all K8S clouds, so please refer to the AWS discovery section.