Cluster Name |
Enter a name for the cluster.
Note The name must be 1 to 63 characters in length, and can contain digits, letters, and
hyphens (-).
|
Cluster Specification |
Select a cluster type. You can select Standard edition or Professional.
Select Standard edition to create a managed edge Kubernetes cluster.
|
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 that you want to use. After
you select a resource group, virtual private clouds (VPCs) and vSwitches are filtered
based on the selected resource group. When you create a cluster, only the VPCs and
vSwitches that belong to the selected resource group are displayed in the console.

|
Kubernetes Version |
The supported Kubernetes versions are displayed. |
Containerd Runtime |
The supported containerd runtime are Docker, Containerd, and Sandboxed-Container.
For more information about containerd, see Comparison of Docker, containerd, and Sandboxed-Container.
|
VPC |
Select a VPC to deploy the cluster. Standard VPCs and shared VPCs are supported.
- Shared VPC: The owner of a VPC (resource owner) can share the vSwitches in the VPC
with other accounts in the same organization.
- Standard VPC: The owner of a VPC (resource owner) cannot share the vSwitches in the
VPC 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 and manage 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 Work with vSwitches.
|
IP Addresses per Node |
If you select Flannel as the network plug-in, you must set 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.
- After you select the VPC and specify the number of IP addresses per node, recommended
values are automatically generated for Pod CIDR Block and Service CIDR. The system
also provides the maximum number of nodes that can be deployed in the cluster and
the maximum number of pods that can be deployed on each node. You can modify the values
based on your business requirements.
|
Pod CIDR Block |
If you select Flannel as the network plug-in, 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 |
Configure SNAT |
By default, an ACK cluster cannot access the Internet. If the VPC that you select
for the cluster cannot access the Internet, you can select Configure SNAT for VPC. This way, ACK will create a NAT gateway and configure SNAT rules to enable Internet
access for the VPC.
|
Access to API Server |
By default, an internal-facing SLB instance is created for the Kubernetes API server
of the cluster. You can modify the specification of the SLB instance. For more information,
see Instance types and specifications
Notice If you delete the SLB instance, you cannot access the Kubernetes API server of the
cluster.
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 associated
with an SLB instance. Port 6443 used by the API server is opened on master nodes.
You can connect to and manage the cluster by using kubeconfig files over the Internet.
- If you clear this check box, no EIP is created. You can connect to and manage the
cluster by using kubeconfig files only from within the VPC.
Note Edge nodes interact with the API server in the cloud over the Internet. If you clear
Expose API Server with EIP, the edge nodes cannot connect to the cluster in the cloud. As a result, the created
cluster cannot be used in edge computing scenarios.
|
RDS Whitelist |
Configure the whitelist of the ApsaraDB RDS instance. Add the IP addresses of nodes
in the cluster to a whitelist of the ApsaraDB RDS instance.
Note To enable an ApsaraDB RDS instance to access the cluster, you must make sure that
the instance is deployed 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 about security groups, see Overview.
|
Deletion Protection |
Specify whether to enable deletion protection for the cluster. Deletion protection
prevents the cluster from being deleted in the console or by calling the API. This
prevents user errors.
|
Resource Group |
The resource group that owns the cluster to be created. Each resource can belong only
to one resource group. You can regard a resource group as a project, an application,
or an organization based on your business scenarios. For more information, see Resource groups.
|