ACK Edge Pro and Basic cluster comparison

Item

ACK Edge Pro

ACK Edge Basic

Cluster size

• Host network mode: up to 1,000 nodes.

• Container network mode: up to 200 nodes.

Cluster size depends on the pod network type.

Up to 10 nodes.

SLA

A service availability of 99.95% is guaranteed for regional clusters, and 99.50% for zonal clusters. For more information, see Container Service for Kubernetes Service Level Agreement.

Not provided.

Scenarios

• Production and testing environments.

• Cost-sensitive workloads.

Supports up to 10 nodes with no control plane SLA. Suitable for individual learning and testing.

Billing methods

You are charged for cluster management based on the number of clusters, and for node management based on the number of edge nodes connected to the cloud. You are also charged for Alibaba Cloud resources used by your ACK Edge clusters. See ACK Edge cluster billing.

You are not charged for cluster management. However, you are still charged for node management based on the number of edge nodes connected to the cloud. You are also charged for Alibaba Cloud resources used by your ACK Edge clusters. See ACK Edge cluster billing.

Feature

ACK Edge Pro

ACK Edge Basic

Customize ACK Pro control plane component parameters

kube-apiserver metrics

High-frequency cold/hot backup and geo-disaster recovery of etcd

Monitoring metrics for the etcd component

Gang scheduling

Enable CPU topology-aware scheduling

Topology-aware GPU scheduling

GPU Sharing Professional Edition

Support for Secret encryption by using KMS

Managed node pools

Item

Differences between ACK Edge clusters and ACK Pro clusters

References

Clusters

Create clusters

Network plug-ins and container CIDR blocks differ between the two cluster types. See How to select a network plugin.

Create a cluster

Update clusters

• ACK Edge clusters do not support auto updates.

• Edge node pools use a different update method than on-cloud node pools in ACK Edge clusters.

Update a cluster

Connect to clusters

Connecting to ACK Edge clusters works the same as ACK Pro clusters.

• Obtain the kubeconfig file and connect to the cluster using kubectl.

• Connect clusters with kubectl on Workbench or CloudShell

• Cluster access control

• Delete kubeconfig files

Manage clusters

Managing ACK Edge clusters works the same as ACK Pro clusters.

• View cluster information

• Cluster lifecycle

• Configure cluster security groups

• Customize ACK Pro control plane component parameters

• Hot migration from ACK Basic clusters to ACK Pro clusters

Delete clusters

After deleting an edge node pool, manually uninstall system components from the nodes. See Remove edge nodes.

Delete an ACK Edge cluster

Nodes and node pools

• On-cloud node pools in ACK Edge clusters have the same capabilities as node pools in ACK Pro clusters.

• An edge node pool in an ACK Edge cluster manages nodes across regions, such as ECS nodes in different regions, data center nodes, nodes from other cloud providers, and nodes in factories, stores, vehicles, and ships.

• Edge node pools in ACK Edge clusters support node autonomy and offline O&M.

• Node pool overview

• Node management

• Configure edge node autonomy

• Offline O&M for edge nodes

Storage

• The csi-plugin and csi-provisioner components in ACK Edge clusters are the same as the CSI plug-in in ACK clusters, and on-cloud nodes use CSI identically. See CSI-based storage solutions.

• Storage types supported by edge nodes in an ACK Edge cluster vary by node type and connection mode.

Storage management

Applications

ACK Edge clusters provide additional workloads and extensions for application management.

• Manage YurtAppSets: ACK Edge provides YurtAppSets to centrally manage multiple workloads, such as Deployments, across regions.

• DaemonSet update extensions: When edge networks disconnect from the cloud, DaemonSet updates may stall. ACK Edge provides AdvancedRollingUpdate and OTA update model extensions to address this.

• Node Pool Application Set Management

• DaemonSet upgrade models

Networks

• Edge nodes connect to ACK Edge clusters in public or private network mode.

• ACK Edge clusters support the Flannel and Terway Edge network plug-ins.

• ACK Edge clusters provide Raven for cross-network-domain communication and efficient cloud-edge operations in multi-region environments.

• ACK Edge clusters support Service topology and port isolation for NodePort Services.

• Ingress controller deployment in ACK Edge clusters differs from ACK Pro clusters.

• Network management

• How to select a network plugin

• The Raven cross-domain O&M communication component

• Configure NodePort listening based on node pools

• Service topology for node pools

• Ingress overview

Auto scaling

• Workload and node scaling capabilities are the same as ACK Pro clusters.

• ACK Edge clusters do not support Elastic Container Instance-based auto scaling.

Auto scaling

Scheduling

Scheduling capabilities are the same as ACK Pro clusters.

Scheduling

O&M and security

• Observability capabilities are the same as ACK Pro clusters.

• ACK Edge clusters do not support the AIOps suite.

• ACK Edge clusters do not support cost insights from the cost management suite.

• ACK Edge clusters do not support sandboxed containers, confidential computing, or automatic image signature verification.

• Observability

• Security architecture overview

• Cost suite

Heterogeneous resources

• GPU-accelerated edge nodes use a different connection mode than in ACK Pro clusters.

• ACK Edge clusters support all cloud-native AI suite capabilities except GPU memory isolation.

• Add a GPU node

• Cloud-native AI suite

Developer tools

Developer tools are the same as ACK Pro clusters.

• API

• CLI

• SDK

• Terraform