Hybrid cloud node pool overview

Updated at:

A hybrid cloud node pool lets you add computing resources from on-premises data centers or multicloud environments as nodes in an ACK managed Pro cluster for centralized management. This reduces the complexity of managing heterogeneous environments and enables elastic resource scheduling, so your workloads stay highly available.

Introduction to hybrid cloud node pools

Scope

Features

  • Unified resource access: Adds server resources from on-premises data centers or multicloud environments to an ACK managed Pro cluster in a standardized way. The deployment, O&M, monitoring, upgrade, and security control experience matches that of ECS nodes in the cloud. This significantly reduces the complexity of managing heterogeneous environments.

  • Deep capability integration: Integrates the core capabilities of an ACK managed Pro cluster, such as auto scaling, observability (monitoring, logs, and distributed tracing), security hardening, storage, and networking. This ensures a highly consistent technology stack across cloud and on-premises environments.

  • High-performance networking: Uses the Terway Hybrid network plugin to enable container network connectivity between cloud and on-premises environments. It also supports the NodeLocal DNSCache add-on, which provides a DNS cache in your on-premises data center. The cache improves DNS performance and stability, and reduces the load on the leased line.

  • Flexible capacity expansion: Addresses insufficient cloud resource inventory or capacity limits in a single region. Introduces cloud resource pools to extend cluster capacity flexibly, which helps ensure business continuity and high availability.

image.png

Billing

When you use a hybrid cloud node pool in an ACK managed Pro cluster, the fees consist of three parts: a cluster management fee, a hybrid cloud node management fee, and cloud product resource fees.

Comparison of node pool features

Feature

Node pools

Hybrid cloud node pools

Create, edit, delete, and view

  • Create node pools in the console and configure basic information, network settings, instance specifications, storage configurations, and the expected number of nodes.

  • Adjust the configurations of existing node pools. For more information about the editable configuration items and important considerations, see the referenced document.

  • Delete node pools when they are no longer needed. The node release behavior depends on whether the expected number of nodes is enabled for the node pool and the billing method of the nodes.

  • View the details of a node pool, including basic configuration information, resource monitoring dashboards, node lists, and scaling activities.

For more information, see Create and manage node pools.

  • Create a hybrid cloud node pool in the console and configure its basic information and network settings.

  • Modify some configurations of an existing hybrid cloud node pool.

  • Delete a hybrid cloud node pool when its hybrid cloud nodes are no longer needed.

  • View the details of a hybrid cloud node pool, including basic configuration information, resource monitoring dashboards, and the list of hybrid cloud nodes.

For more information, see Create and manage hybrid cloud node pools.

Manual or automatic scaling

  • Manually adjust the expected number of nodes in a node pool to scale it in or out. This keeps the number of nodes at the desired level and helps save resource costs.

    Certain non-standard removal, modification, and release operations may prevent the node pool from scaling out as expected. For more information, see the referenced document.

  • Configure a node autoscaling solution to automatically scale node resources when the cluster's capacity cannot meet the scheduling requirements of application pods.

For more information, see Manually scale a node pool and Node scaling.

Not supported

Add existing nodes

Use the Add Existing Nodes feature to add a purchased ECS instance to an ACK cluster as a worker node or to add a worker node back to a node pool after it was removed. This feature has some limitations and important considerations. For more information, see the referenced document.

For more information, see Add existing nodes.

You must first register your own hybrid cloud nodes as Alibaba Cloud managed instances before you add them to a Container Service for Kubernetes (ACK) cluster for unified management.

For more information, see Add hybrid cloud nodes.

Remove nodes

If you no longer need certain nodes, you can remove them from the cluster or node pool. Follow the standard procedures to avoid unexpected behavior.

For more information, see Remove a node from a cluster or node pool.

If you no longer need certain hybrid cloud nodes, you can remove them from the cluster or the hybrid cloud node pool.

Important

Removing a hybrid cloud node from a hybrid cloud node pool does not unregister it as an Alibaba Cloud managed instance.

For more information, see Remove hybrid cloud nodes.

Upgrade the kubelet version

You can also use the automatic cluster upgrade feature to upgrade the kubelet and the container runtime automatically.

Upgrade the kubelet and containerd versions of the nodes in a node pool.

For more information, see Upgrade a node pool.

Upgrade the kubelet and containerd versions of the hybrid cloud nodes in a hybrid cloud node pool.

Important

ACK managed ECS nodes can be upgraded automatically, whereas Alibaba Cloud managed instances nodes must be upgraded manually.

Change the operating system

Upgrade the operating system version or change the operating system type. For example, you can switch from an end-of-life (EOL) operating system to ContainerOS or Alibaba Cloud Linux.

For more information, see Change the operating system.

Not supported

CVE vulnerability remediation

You can also enable automated O&M capabilities so that ACK fixes OS CVE vulnerabilities automatically.

Manually scan for CVE vulnerabilities and fix security vulnerabilities in the node operating system. Some CVE vulnerability fixes require a node restart. For more information about this feature and its considerations, see the referenced document.

For more information, see Manual OS CVE patching.

Provides CVE vulnerability scanning and remediation for Kubernetes components such as containerd and kubelet in a hybrid cloud node pool.

Customize kubelet parameters for a node pool

Customize kubelet parameters for nodes at the node pool level to adjust node behavior. For example, you can adjust cluster resource reservations to manage resource allocation.

For more information, see Customize node pool kubelet configurations.

Customize the kubelet parameters of hybrid cloud nodes at the hybrid cloud node pool level to adjust node behavior. For example, adjust cluster resource reservations to manage resource usage.

Customize OS parameters for a node pool

Customize OS parameters for nodes at the node pool level to tune system performance.

For more information, see Customize node pool OS parameters.

Use Cloud Assistant to run preset commands for kernel parameter tuning.

Shared responsibility for security

The shared responsibility model is as follows:

  • Alibaba Cloud is responsible for:

    • The security of the control plane infrastructure, including cloud resources such as computing, storage, and networking.

    • Vulnerability patches and version updates at the Kubernetes component level for hybrid cloud node pools.

  • You are responsible for:

    • The network connectivity between hybrid cloud nodes and the ACK control plane.

    • The stability and security of the hybrid cloud nodes themselves, and of the operating system on these nodes, including but not limited to security vulnerability fixes and version updates.

    • The security protection of the business applications that you deploy, and the security configuration and updates of the hybrid cloud nodes.

Operating system compatibility

The following table lists the operating systems that hybrid cloud node pools support. To use other operating systems, contact your account manager for an evaluation.

Image type

Platform

System architecture

Image name (including version information)

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 Edition

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