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 left navigation pane, click Clusters.

2. At the top left of the page, select the resource group and region of the target resource.

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

4. Click the ACK One Registered Cluster tab and follow the on-screen instructions to configure the cluster.

   Parameter	Description
   Cluster Name	Enter a custom name for the cluster.
   Region	The region where the cluster resources, such as ECS instances and cloud disks, are located. The closer the region is to your users and resource deployment region, the lower the network latency.
   IPv6 Dual-stack	This feature is only available for Kubernetes 1.22 and later and only supports Terway. It cannot be used with the elastic Remote Direct Memory Access (eRDMA) feature The cluster supports both IPv4 and IPv6 protocols. However, communication between worker nodes and the control plane still uses IPv4 addresses. Make sure that: The cluster VPC supports IPv6 dual-stack. When using Terway in shared ENI mode, the node's instance type must support IPv6 and have the same number of supported IPv4 and IPv6 addresses.
   VPC	The virtual private cloud (VPC) for the cluster. For high availability, select two or more different zones. Automatic creation: ACK creates a corresponding vSwitch in each selected zone. Use existing: Select a vSwitch to specify the zone for the cluster. You can create a new vSwitch or use an existing one. We recommend using standard private CIDR blocks for the cluster VPC, such as 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. If you have special requirements, go to Quota Center to apply for permission to use a public CIDR block to create a cluster. Cloud resources and billing: VPC
   vSwitch	Select an existing vSwitch from the list based on the zone, or click Create vSwitch to create a new one. The cluster control plane and the default node pool will use the vSwitch specified here. We recommend selecting vSwitches in multiple different zones to ensure high availability for the cluster.
   Security Group	When using an existing VPC, you can choose to Select Existing Security Group This security group is applied to the cluster control plane, the default node pool, and any node pools that do not have a custom security group specified. Compared to basic security groups, advanced security groups can contain more private IP addresses but do not support intra-group connectivity. For more information, see Security group classification. Automatic creation: All outbound traffic is allowed by default. Inbound traffic is allowed based on the recommended configuration. If you modify the rules later, ensure that the 100.64.0.0/10 CIDR block is allowed for inbound traffic. This CIDR block is used to access other Alibaba Cloud services for operations such as pulling images and querying basic ECS information. Use existing: ACK does not configure additional access rules for the security group by default. You must manage the security group rules yourself to avoid access issues. For more information, see Configure cluster security groups.
   Access to API Server	ACK automatically creates a pay-as-you-go private-facing Classic Load Balancer (CLB) instance as the internal endpoint for the API Server. This CLB instance cannot be reused or deleted. If deleted, the API Server will become inaccessible and cannot be recovered. To use an existing CLB instance, submit a ticket. After you select Use Existing Gateway for VPC, you can set SLB Source to Use Existing Gateway. You can choose to enable Expose API server with EIP. Open: Binds an EIP to the API Server's private-facing CLB instance, allowing you to access and manage the cluster from the public network. This does not mean that resources within the cluster can access the public network. To allow cluster resources to access the public network, you must select Configure SNAT for VPC. Not open: You can only connect to and operate the cluster using the kubeconfig file from within the VPC. To enable this later, see Access the API server over the internet. Starting from December 1, 2024, new CLB instances will incur an instance fee. For more information, see Billing item adjustment for Classic Load Balancer (CLB). Cloud resources and billing: CLB, EIP

   Advanced options (optional)

   Expand Advanced Options (Optional) to configure Deletion Protection, Resource Group, and other settings.

   Parameter	Description
   Cluster Deletion Protection	We recommend enabling this feature to prevent accidental deletion of the cluster through the console or OpenAPI.
   Resource Group	Assign the cluster to the selected resource group for easier permission management and cost allocation.
   Label	Bind key-value tags to the cluster to identify cloud resources.

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

   After the cluster is created, its status is Waiting for Connection.