Edge node pools allow you to connect IDC servers, third-party cloud servers, and edge computing resources to a cluster over the public network for unified management. They provide a consistent deployment, O&M, and upgrade experience with edge autonomy to keep your workloads stable even over unreliable networks. This topic covers the features, scope, billing, and comparisons with other node pool types.
Features
ACK managed Pro cluster edge node pools are currently in whitelist-based beta. To request access, contact your account manager.
Unlike ECS node pools, which support only Alibaba Cloud ECS instances, edge node pools are designed for edge environments with unreliable, high-latency networks. You can register IDC servers, third-party cloud resources, or edge computing devices as Alibaba Cloud managed instances and add them to a cluster. Edge node pools also provide edge-native capabilities including node autonomy and network autonomy.
Unified resource access: Connect IDC servers, third-party cloud servers, and edge computing resources to ACK managed Pro cluster over the public network, and manage them with the same deployment, O&M, monitoring, upgrade, and security controls used for cloud-based ECS nodes.
Deep capability integration: Integrate ACK managed Pro cluster core capabilities — including auto scaling, observability (monitoring, logging, and tracing), security hardening, and networking — so your technology stack stays consistent across cloud and on-premises environments.
Elastic capacity scaling: Overcome cloud resource shortages or capacity limits in a single region by scaling cluster capacity with on-premises resources, helping maintain service continuity and high availability.
Enhanced edge autonomy: Node autonomy and network autonomy keep edge nodes and workloads running when network connectivity to the cloud is weak or intermittent.
Diverse application scenarios: Edge node pools support IoT gateway devices, GPU heterogeneous computing, edge intelligence, smart buildings, smart factories, live video streaming, online education, CDN, and more.
Billing
Using edge node pools in ACK managed Pro cluster incurs the following fees:
Edge node management fee: Free during the beta period.
Cloud resource fees: Charges for other Alibaba Cloud services you use (such as Edge Node Service (ENS)) are billed according to each service's pricing.
Node pool comparison
Edge node pools vs. ECS node pools
Feature | Edge node pool | |
Adding nodes | Register your own resources (IDC servers, edge computing resources, or third-party servers) as Alibaba Cloud managed instances, and then add them to an edge node pool for unified management. | Uses Elastic Compute Service (ECS). You can create new instances or use existing ECS instances. |
Scaling node pool | Not supported. | Supported. |
Upgrade kubelet | You must manually upgrade kubelet. | You can Update a node pool nodes in batches through the console. |
Change operating system | Not supported. | Supported. You can Change the operating system (for example, switching from an EOL operating system to ContainerOS or Alibaba Cloud Linux). |
Storage | Supports native Kubernetes volume types (such as EmptyDir, HostPath, Secret, and ConfigMap). OSS, NAS, cloud disks, and local storage are not supported. | Supports native Kubernetes volume types as well as Alibaba Cloud storage services including OSS, NAS, cloud disks, and local storage. |
Logging | Supports Collect container logs by using a Kubernetes CRD, Simple Log Service console and environment variables. | |
Observability | Supports collecting kubelet, node-exporter, and gpu-exporter metrics through Alibaba Cloud Prometheus monitoring. Custom metric collection is not supported. | Supports collecting basic metrics through Alibaba Cloud Prometheus monitoring, and also supports Collect custom metrics. |
CVE vulnerabilities patching | Not supported. | Supports Automatically Patching OS CVE vulnerabilities for a node pool. |
Edge node pools vs. hybrid cloud node pools
Both edge node pools and hybrid cloud node pools allow you to connect resources from data centers and third-party cloud providers. However, they differ in features and use cases:
Item | Edge node pool | Hybrid cloud node pool |
Use cases | Suitable for scenarios where nodes are distributed across different regions or network environments and a leased line connection is unavailable. | Suitable for scenarios where nodes are centrally located in the same region or network environment, allowing for unified access through a leased line connection. |
Node-to-cluster connection | Nodes are registered as Alibaba Cloud managed instances and connected over a public network connection. | Nodes are registered as Alibaba Cloud managed instances and connected through a leased line connection. |
Node-to-node network connectivity requirement | Node-to-node communication is not required. | Node-to-node communication is required. |
Network plugin | Uses Terway Hybrid, which supports only Overlay mode. | Uses Terway Hybrid, which supports both Underlay and Overlay modes. |
CoreDNS component | Only yurt-coredns-controlplane is supported. | Supports both CoreDNS and yurt-coredns-controlplane. |
Shared responsibility model
When you use edge node pools, security responsibilities are shared between you and Alibaba Cloud as follows:
Alibaba Cloud is responsible for:
The security of the control plane infrastructure, including cloud resources for computing, storage, and networking.
Vulnerability patches and version updates for Kubernetes components in edge node pools.
You are responsible for:
The network connectivity between your edge nodes and the ACK control plane.
The stability and security of the edge nodes and their operating systems, including fixing security vulnerabilities and performing version updates.
The security of your deployed applications and the management of security configurations and updates for your edge nodes.
Operating system compatibility
Edge node pools support the following operating systems:
To connect nodes that use other operating systems, contact your account manager for an evaluation.
Image type | Platform | System architecture | Image name (including version) | Image ID |
Alibaba Cloud Linux 3.2104 LTS 64-bit Container-Optimized Edition | Alibaba Cloud | x86_64 | Alibaba Cloud Linux 3.2104 Container-Optimized | aliyun_3_x64_20G_container_optimized_alibase_20251215.vhd Uses cgroup v2 by default. |
Alibaba Cloud Linux 3 | Alibaba Cloud | x86_64 | Alibaba Cloud Linux 3.2104 LTS 64-bit | aliyun_3_x64_20G_alibase_20240528.vhd |
Alibaba Cloud Linux 3 (ARM) | Alibaba Cloud | arm64 | Alibaba Cloud Linux 3.2104 LTS 64-bit ARM Edition | aliyun_3_arm64_20G_alibase_20240528.vhd |
Alibaba Cloud Linux UEFI 3 | Alibaba Cloud | x86_64 | Alibaba Cloud Linux UEFI 3.2104 Security Enhanced | aliyun_3_x64_20G_uefi_alibase_20230727.vhd |
Red Hat | Red Hat | x86_64 | Red Hat Enterprise Linux (RHEL) 9.3 64-bit | Red Hat Enterprise Linux 9.3 64-bit RHEL 9 and later use cgroup v2 by default. |
Ubuntu | Ubuntu | x86_64 | Ubuntu 22.04 64-bit Ubuntu 24.04 64-bit | None |