Alibaba Cloud Service Mesh:Manage Kubernetes Clusters Imported by Using a kubeconfig File

Known limitations

The following limitations apply to the ASM console and related features when a cluster is added to an ASM instance by importing a kubeconfig file:

• Ingress gateways — You cannot create a LoadBalancer ingress gateway in the ASM console. Instead, create the ingress gateway by using a custom resource definition (CRD). For more information, seeASM Gateway CRDs. The Kubernetes cluster must support LoadBalancer Services.

• Traffic lanes — You cannot use traffic lanes in the ASM console. Instead, configure traffic lanes by using CRDs. For more information, seeASMSwimLaneGroup and ASMSwimLane CRDs.

• Plugin binding — You cannot bind a plugin to a specific workload in the plugin center. Instead, deploy plugins by using the EnvoyFilterTemplate CRD. For more information, seeEnvoyFilterTemplate and EnvoyFilterTemplateBinding CRDs.

• Log collection — You cannot send gateway and mesh proxy logs to Simple Log Service (SLS). Instead, use your own log collection solution to collect the standard output of the istio-proxy container in the cluster.

• Metric collection — You cannot send monitoring metrics to Managed Service for Prometheus. Instead, use a self-managed Prometheus instance to collect mesh monitoring metrics. For more information, seeIntegrate a self-managed Prometheus instance for mesh monitoring.

• Service discovery — You cannot use Service Discovery Selectors in the ASM console.

• CNI plug-in — You cannot use the ASM CNI Plug-in.

• Kubernetes service management — You cannot use Kubernetes Service Management in the ASM console.

• Sidecar auto-injection — You cannot use the Sync Sidecar Auto-Injecttion from Kubernetes Cluster feature. The Sync Automatic Sidecar Injection to Kubernetes Cluster and Enable/Disable Sidecar Auto Injection features remain available.

Prerequisites

ASM instance

• An ASM instance whose version is 1.22 or later. For instructions, seeCreate an ASM instance.

• Public network access enabled for the ASM control plane by attaching elastic IP addresses (EIPs). For instructions, seeAttach or detach an EIP for the ASM control plane.

Kubernetes cluster and kubeconfig file

Because the cluster is added to the ASM instance by importing a kubeconfig file, make sure that the following requirements are met:

• The Kubernetes cluster has public network access.

• The kubeconfig file of the cluster contains a public endpoint.

• The kubeconfig file has cluster administrator permissions on the corresponding Kubernetes cluster.

Add a Kubernetes cluster by importing a kubeconfig file

1. Log on to the ASM console. In the left-side navigation pane, choose Service Mesh > Mesh Management.

2. On the Mesh Management page, click the name of the ASM instance. In the left-side navigation pane, choose Cluster & Workload Management (Data Plane) > Kubernetes Clusters.

3. Click Add.

4. On the Add Kubernetes Cluster page, click the Add Kubernetes Cluster by Using Kubeconfig tab.

5. Enter the cluster Name. In the Cluster Kubeconfig field, paste the content of a kubeconfig file that can access the cluster and has cluster administrator permissions. Then, click OK.

   Important

   The cluster and the kubeconfig file must meet the requirements described in Prerequisites.

6. In the Note dialog box, click OK.

   After the cluster is added, choose Instance Information > Base Information. The Status of the ASM instance changes to Updating. After a few seconds (the duration depends on the number of clusters being added), click Refresh in the upper-right corner of the page. The Status of the ASM instance changes to Running. Information about the added cluster is displayed on the Kubernetes Clusters page.