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. In the top-left corner of the page, select the resource group and region where your target resources reside.

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 cluster name.
   Region	The region where cluster resources (such as ECS instances and cloud disks) are located. The closer the region is to your location and where your resources are deployed, the lower the network latency.
   IPv6 Dual-stack	Supported only for Kubernetes 1.22 or later, only with Terway, and cannot be used together with eRDMA. The cluster supports both IPv4 and IPv6 protocols, but communication between worker nodes and the control plane still uses IPv4 addresses. Ensure the following: The cluster VPC supports IPv6 dual-stack. When using Terway in shared ENI mode, the instance type of the node must support IPv6 and have the same number of assignable IPv4 and IPv6 addresses.
   VPC	The VPC for the cluster. To ensure high availability, we recommend selecting two or more zones. Auto-create: ACK creates a vSwitch in each selected zone. Use existing: Select a vSwitch to specify the cluster zone. You can create a new vSwitch or use an existing one. We recommend using standard private CIDR blocks for the cluster VPC (for example, 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16). If you have special requirements, apply at the Quota Center (Create a cluster using a public CIDR block VPC). Cloud resource and billing information: VPC
   vSwitch	Select an existing vSwitch by zone from the list, or click Create vSwitch to create a new one. The control plane and default node pool use the specified vSwitch. For better high availability, we recommend selecting vSwitches in multiple zones.
   Security Group	When using an existing VPC, you can select Select Existing Security Group This security group applies to the cluster control plane, default node pool, and any node pool without a custom security group. Compared with basic security groups, enterprise security groups can accommodate a larger number of private IP addresses but do not support intra-group connectivity. For more information, see Security Group Classification. Auto-create: All outbound traffic is allowed by default. Inbound rules follow recommended configurations. If you modify rules later, ensure inbound access to the 100.64.0.0/10 CIDR block is allowed. This CIDR block is used to access other Alibaba Cloud services for operations such as image pulling and querying ECS basic information. Use existing: ACK does not add extra access rules to the security group. You must manage security group rules yourself to avoid access issues. For details, see Configure cluster security groups.
   Access to API Server	ACK automatically creates a pay-as-you-go private CLB instance as the internal endpoint for the API Server. This CLB instance cannot be reused or deleted. If deleted, the API Server becomes inaccessible and cannot be restored. To use an existing CLB instance, submit a ticket. After selecting Use Existing Gateway for the VPC, you can set the SLB Source to Use Existing Gateway. You can optionally enable Expose API server with EIP. Enabled: Binds an EIP to the private CLB instance of the API Server, allowing public network access to manage the cluster. This does not grant public network access to resources inside the cluster. To allow cluster resources to access the public network, select Configure SNAT for VPC. Disabled: Allows cluster connection and management via KubeConfig only from within the VPC. To enable this later, see Enable public network access to API Server. Starting December 1, 2024, newly created CLB instances will no longer support Subscription billing, and will incur instance fees. For details, see [Product Announcement] Discontinuation of subscription billing for new cluster API Server CLB instances, Adjustment announcement for Classic Load Balancer CLB billing items. Cloud resource and billing information: 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 to prevent accidental cluster deletion via 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 as cloud resource identifiers.

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.