Create a managed edge Kubernetes cluster

Managed edge Kubernetes clusters are designed to bring cloud computing to edges (clients). Managed edge Kubernetes clusters can be created, managed, and maintained in the Container Service for Kubernetes (ACK) console. ACK is a platform built on top of the edge computing infrastructure. It is also integrated with cloud computing and edge computing. This topic describes how to create a managed edge Kubernetes cluster in the ACK console.

1. Log on to the Container Service for Kubernetes (ACK) console.
2. In the left-side navigation pane of the ACK console, click Clusters.
3. In the upper-right corner of the Clusters page, click Create Kubernetes Cluster.
4. Click the Managed Edge Kubernetes tab and configure the cluster.

   Configure basic settings of the cluster.

   Parameter	Description
   Cluster Name	Enter a name for the ACK cluster. Note The name must be 1 to 63 characters in length, and can contain digits, letters, and hyphens (-).
   Region	Select a region to deploy the cluster.
   Resource Group	Move the pointer over All Resources at the top of the page and select the resource group to which the cluster belongs. The name of the selected resource group is displayed, as shown in the following figure.
   Kubernetes Version	The supported Kubernetes versions are displayed.
   VPC	Select a virtual private cloud (VPC) to deploy the cluster. Shared VPCs and standard VPCs are supported. Shared VPC: The owner of a VPC (resource owner) can share vSwitches in the VPC within the account of the owner with other accounts in the same organization. Standard VPC: The owner of a VPC (resource owner) cannot share vSwitches in the VPC within the account of the owner with other accounts. Note ACK clusters support only VPCs. You can select a VPC from the drop-down list. If no VPC is available, click Create VPC to create one. For more information, see Create a VPC.
   VSwitch	Select vSwitches. You can select up to three vSwitches that are deployed in different zones. If no vSwitch is available, click Create VSwitch to create one. For more information, see Create a vSwitch.
   Pod CIDR Block	If you select Flannel, you must set Pod CIDR Block. The CIDR blocks specified by Pod CIDR Block and Service CIDR cannot overlap with the CIDR block of the VPC and the CIDR blocks of the existing ACK clusters in the VPC. You cannot modify the CIDR blocks after the cluster is created. The Service CIDR block cannot overlap with the Pod CIDR block. For more information about subnetting for ACK clusters, see Plan CIDR blocks for an ACK cluster.
   Service CIDR
   IP Addresses per Node	If you select Flannel, you must set the number of IP addresses per node. Note IP Addresses per Node specifies the maximum number of IP addresses that can be assigned to each node. We recommend that you use the default value.
   Configure SNAT	By default, an ACK cluster cannot access the Internet. If the VPC that you select for the ACK cluster cannot access the Internet, you can select Configure SNAT for VPC. Then, ACK creates a Network Address Translation (NAT) gateway and configures Source Network Address Translation (SNAT) entries to enable Internet access for the VPC.
   Access to API Server	By default, an internal-facing Server Load Balancer (SLB) instance is created for the cluster API server. You can modify the specifications of the SLB instance. For more information, see Specification. Notice If you delete the SLB instance, you cannot access the API server. Select or clear Expose API Server with EIP. The ACK API server provides multiple HTTP-based RESTful APIs, which can be used to create, delete, modify, query, and monitor resources, such as pods and Services. If you select this check box, an elastic IP address (EIP) is created and attached to an Internet-facing SLB instance. Port 6443 used by the API server is opened on master nodes. You can connect to and manage the ACK cluster by using kubeconfig over the Internet. If you clear this check box, no EIP is created. You can connect to and manage the ACK cluster only by using kubeconfig from within the VPC. Note Edge nodes need to call the API over the Internet. If you clear Expose API Server with EIP, the edge nodes cannot be connected to the edge cluster. As a result, the created cluster cannot be used in edge computing scenarios.
   RDS Whitelist	Set the Relational Database Service (RDS) whitelist. Add the IP addresses of nodes in the cluster to the RDS whitelist. Note To enable an RDS instance to access the cluster, you must deploy the RDS instance in the VPC where the cluster is deployed.
   Security Group	You can select Create Basic Security Group, Create Advanced Security Group, or Select Existing Security Group. For more information, see Overview.

   Configure advanced settings of the cluster.

   Parameter	Description
   Labels	Add labels to nodes. Enter a key and a value, and click Add. Note Key is required. Value is optional. Keys are not case-sensitive. A key must be 1 to 64 characters in length, and cannot start with aliyun, http://, or https://. Values are not case-sensitive. A value must be 1 to 128 characters in length and cannot start with http:// or https://. This parameter can be empty. The keys of labels that are added to the same resource must be unique. If you add a label with a used key, the label overwrites the one that uses the same key. You can add up to 20 labels to each resource. If you add more than 20 labels to a resource, all labels become invalid. You must remove excess labels for the remaining labels to take effect.
   Deletion Protection	Specify whether to enable deletion protection. If you select this check box, the ACK cluster cannot be deleted in the console or by calling the API. This prevents user errors.

5. Click Next:Worker Configurations to configure worker nodes.
   Note In a managed edge Kubernetes cluster, you must configure at least one worker node to deploy components.

   Parameter	Description
   Instance Type	You can select multiple instance types. For more information, see Instance families. Note To use advanced features such as logging, monitoring, and reverse tunneling, you must deploy the related components in the cloud. Therefore, you must create at least one ECS instance as a worker node.
   Selected Types	The selected instance types are displayed.
   Quantity	Specify the number of worker nodes (ECS instances) to be created.
   System Disk	Configure the system disks of worker nodes. SSDs and ultra disks are supported.
   Mount Data Disk	Enhanced SSDs, SSDs, and ultra disks are supported. Note You can select Enable Backup to back up disk data. If you select an enhanced SSD as the system disk, you can also set a custom performance level for the disk. You can select higher performance levels for enhanced SSDs with larger storage capacities. For example, you can select performance level 2 for an enhanced SSD with a storage capacity of more than 460 GiB. You can select performance level 3 for an enhanced SSD with a storage capacity of more than 1,260 GiB. For more information, see Capacity and PLs of ESSDs.
   Logon Type	Note You must set the logon type if you select Install CloudMonitor Agent on ECS Instance or Enable Log Service.
   Key Pair

6. Click Next:Component Configurations to configure components.

   Parameter	Description
   Monitoring Agents	Select whether to install the Cloud Monitor agent. If you select Install CloudMonitor Agent on ECS Instance, you can view monitoring information about the nodes in the Cloud Monitor console.
   Log Service	Specify whether to enable Log Service. You can select an existing Log Service project or create a new one. By default, Enable Log Service is selected. When you create an application, you can perform a few simple steps to enable Log Service. For more information, see Use Log Service to collect container logs. You can also select or clear Collect Logs of Control Plane Components. If you select this check box, logs of components on the ACK control plane are collected to the specified Log Service project within your account. For more information, see Collect log data of control plane components from a managed Kubernetes cluster. Note By default, Collect Logs of Control Plane Components is selected for a professional managed Kubernetes cluster.
   Workflow Engine	Specify whether to enable Alibaba Cloud Genomics Compute Service (AGS). If you select this check box, the system automatically installs the AGS workflow plug-in when the system creates the ACK cluster. If you clear this check box, you must manually install the AGS workflow plug-in. For more information, see Introduction to AGS CLI.

7. Click Next:Confirm Order.
8. Read Terms of Service, select the check box, and then click Create Cluster.
   Note It requires about 10 minutes to create a managed edge Kubernetes cluster.

Result

After the cluster is created, you can find the newly created cluster on the Clusters page in the ACK console.

Click View Logs in the Actions column. On the Log Information page, you can view the cluster log. To view detailed log information, click Stack events.

On the Clusters page, find the newly created cluster and click Details in the Actions column. On the details page of the cluster, you can click the Basic Information tab to view basic information about the cluster and click the Connection Information tab to view information about how to connect to the cluster.

The following information is displayed.

• API Server Public Endpoint: the IP address and port that the API server uses to provide services over the Internet. It allows you to manage the cluster by using kubectl or other tools on your terminal devices.
• API Server Internal Endpoint: the IP address and port that the API server uses to provide services within the cluster.
• Testing Domain: the domain name that is used to test Services. The suffix of the domain name is <cluster_id>.<region_id>.alicontainer.com.
  Note To rebind the domain name, click Rebind Domain Name.

You can Use kubectl to connect to an ACK cluster and run the kubectl get node command to view information about the nodes in the cluster.