Container Service for Kubernetes:Create an ACK One registered cluster

Create an ACK One registered cluster

1. Log on to the ACK console. In the navigation pane on the left, click Clusters.

2. In the navigation bar on the top, select the resource group and region where your target resource resides.

3. On the Clusters page, click Create Kubernetes Cluster.

4. Click the ACK One Registered Cluster tab and configure the cluster parameters.

   Configuration item	Description
   Cluster Name	The custom name of the cluster.
   Region	The region of the cluster. The closer the selected region is to the user and the deployed resources, the lower the network latency and the faster the access speed.
   IPv6 Dual-stack	If you enable IPv4/IPv6 dual-stack, a dual-stack cluster is created. Important Only clusters that run Kubernetes 1.22 and later support this feature. IPv4 addresses are used for communication between worker nodes and the control plane. You must select Terway as the network plug-in. If you use the shared elastic network interface (ENI) mode of Terway, the ECS instance type must support IPv6 addresses. To add ECS instances of the specified type to the cluster, the number of IPv4 addresses supported by the ECS instance type must be the same as the number of IPv6 addresses. For more information about ECS instance types, see Overview of instance families. The VPC used by the cluster must support IPv4/IPv6 dual-stack. You must disable IPv4/IPv6 dual stack if you want to use Elastic Remote Direct Memory Access (eRDMA) in an cluster.
   VPC	Configure the VPC of the cluster. You can specify a zone to automatically create a VPC. You can also select an existing VPC in the VPC list.
   VSwitch	Select an existing vSwitch from the vSwitch list or click Create vSwitch to create a vSwitch. The control plane and the default node pool use the vSwitch that you select. We recommend that you select multiple vSwitches in different zones to ensure high availability.
   Security Group	When VPC is set to Select Existing VPC, you can select the Select Existing Security Group option. You can select Create Basic Security Group, Create Advanced Security Group, or Select Existing Security Group. By default, automatically created security groups allow all outbound traffic. When you modify the security group for business purposes, make sure that traffic destined for 100.64.0.0/10 is allowed. This CIDR block is used to access other Alibaba Cloud services to pull images and query basic ECS information. If you select an existing security group, the system does not automatically configure security group rules. This may cause errors when you access the nodes in the cluster. You must manually configure security group rules. For more information, see Configure security groups for clusters.
   Access to API Server	The API server provides various HTTP REST interfaces for managing resource objects (such as pods and Services), including create, read, update, delete, and watch operations. By default, the system creates a pay-as-you-go internal-facing Classic Load Balancer (CLB) instance for the API server to serve as the internal endpoint of the API server in the cluster. To use an existing CLB instance, you must first submit a ticket to request whitelist access. After configuring to use existing VPCs, you can use existing CLB instances as the load balancer source. Specify whether to Expose API server with EIP: If you select this check box, an elastic IP address (EIP) is associated with the internal-facing CLB instance used to expose the API server of the cluster. This way, you can access the API server of the cluster over the Internet. If you clear this check box, no EIP is created. You can use a kubeconfig file to connect to the cluster only from within the VPC and then manage the cluster. Important If you delete the default CLB instance, you cannot access the API server. After binding an EIP to a CLB instance, the API server can receive requests from the public network. However, resources within the cluster cannot access the public network. To allow resources within the cluster to access the public network to pull public images, select the Configure SNAT check box for the VPC. Starting from December 1, 2024, an instance fee will be charged for newly created CLB instances. For more information, see CLB billing adjustments.

   Advanced options (optional)

   Expand Advanced Options (optional) to configure parameters such as cluster deletion protection and resource groups.

   Configuration item	Description
   Cluster Deletion Protection	We recommend that you enable deletion protection in the console or by using API to prevent clusters from being accidentally released.
   Resource Group	Assign the cluster to the selected resource group for easier permission management and cost allocation.
   Tags	Add a label to the cluster. Labels are used to identify cloud resources. A label is a key-value pair.

5. After you complete the configuration, click Create Cluster. The new cluster appears in the cluster list.