Platform Center
Home / Platform management / Clusters / Clusters / Take Over Cluster / Cluster of access / Plug into the Amazon EKS cluster

Plug into the Amazon EKS cluster

Supports connecting deployed Amazon EKS (Amazon Elastic Kubernetes Service) clusters to the platform for unified management.

Prerequisites

Prepare Operation Environment

To comply with the security requirements of AWS EKS, the following steps need to be performed using Cloud Shell.

  1. Ensure network connectivity with the Amazon AWS Console.

  2. Enter the keyword cloudshell in the search bar and open the Cloud Shell feature page .

  3. Check if the region you are currently in is the region where the access cluster is located, if necessary you need to switch to the region where the cluster is located first.

  4. After Cloud Shell is ready, clear the command line and execute the following command:

# Get the list of clusters in the current region，Also check if the current account has sufficient permissions
aws eks list-clusters

# <region-code> Code for the region where the cluster is located，such as us-west-1
# <my-cluster> Name of the cluster to be accessed，Can be obtained from the output of the previous command
aws eks update-kubeconfig --region <region-code> --name <my-cluster>

# KubeConfig The file has been saved in "${HOME}/.kube/config" under the path
# You can save its content as a file，Then upload it to this platform for parsing
cat "${HOME}/.kube/config"
  1. The environment is now ready. In the following steps, such as “Get cluster information” and “Cluster access”, the commands executed for accessing the cluster environment should be performed in Cloud Shell.

Get cluster information

Get Access Cluster Token

The KubeConfig file of a public cloud cluster cannot be directly used to access the cluster.

Please refer to the FAQ How to fetch the kubeconfig file? for obtaining the access token to connect to the cluster.

Cluster of access

  1. In the left navigation bar, click Clusters > Cluster of clusters.

  2. Click on Cluster of access.

  3. Configure the relevant parameters according to the following instructions.

    Parameter Description
    repository The repository that stores the platform components images required by the cluster.
    - Default: The repository configured when deploying the global platform.
    - Private repository: A pre-built repository that stores the platform components. You need to enter the private repository address, port, username, and password to access the repository.
    - Public repository: Use a repository service located on the public network. Before using it, you need to refer to Updating public network repository cloud credentials to obtain repository authentication permissions.
    Cluster Information Note: Please upload the KubeConfig file, which will be automatically parsed and filled in by the platform.

    Cluster Address: The access address of the API Server exposed to the outside of the cluster, used for the platform to access the API Server of the connected cluster.

    CA Certificate: The CA certificate of the connected cluster.

    Authentication Method: The authentication method of the connected cluster. You need to use the token with cluster management permissions created in the previous step for authentication.

  4. Click on Check Connectivity to verify the network connectivity with the connected cluster and automatically identify the type of the connected cluster. The cluster type will be displayed as a badge in the top right corner of the form.

  5. After passing the connectivity check, click on Connect and confirm.

    Tip:

    • Click on the icon on the right side of the cluster in the In Progress state to view the execution progress of the cluster (status.conditions) in the popped-up Execution Progress dialog box.

    • After successful cluster access, you can view key information about the cluster in the cluster list. The status of the cluster will be displayed as normal, and you can perform cluster-related operations.

Network Configuration

To ensure that global is interoperable with the accessed cluster network, you must refer to Access Cluster Network Configuration 。

What’s next

Deployment plugins

After successfully accessing the cluster, you can go to Plugin Management to select the necessary plugins for cluster deployment, including monitoring components, Log Agent, log storage components, etc.

Tip: When deploying the Prometheus monitoring component, you need to open port 11780 in the security group of the nodegroup in the EKS cluster.

Namespace under the tube cluster

After accessing the cluster, you can add the cluster to an existing project by creating a project based on the cluster or by adding a cluster associated with the project , thus associating the newly accessed cluster with the project.

Furthermore, by performing the import namespace operation, existing Kubernetes namespaces within the cluster can be included and managed under the platform’s project.

FAQ

The Add node button is grayened after accessing the cluster. How to add nodes?

Unable to add nodes in the platform interface, please contact the cluster provider to add them.

Which certificates are supported by the certificate management function of the access cluster?

  1. Kubernetes certificate: All access to the cluster only supports viewing the APIServer certificate information in the platform’s certificate management interface. It does not support viewing other Kubernetes certificates and does not support automatic rotation.

  2. Platform Component Certificate: All access to the cluster can view the platform component certificate information in the platform certificate management interface and support automatic rotation.

What other features do not support import to **Amazon EKS clusters **?