Overview of ENS management
Edge Node Service (ENS) provides distributed, elastic computing resources deployed at Internet service provider (ISP) edge locations — close to end users. Running workloads on ENS reduces response latency, lowers compute costs, and offloads traffic from your central cloud nodes.
This topic explains how to manage ENS nodes in an ACK Edge cluster.
How it works
Container Service for Kubernetes (ACK) Edge clusters extend Kubernetes management to ENS instances across multiple regions and ISPs. With ACK Edge clusters, you can unify the management of ENS instances deployed across multiple regions and ISPs through containerization, using the same Kubernetes tooling you already use.
The cluster integrates with two ENS-native capabilities:
ENS disks — cloud-native storage managed through the Container Storage Interface (CSI) plug-in, supporting both static and dynamic volume provisioning
Edge Load Balancer (ELB) — cross-region Service exposure without requiring a central load balancer
Control plane connectivity options
Centralized management of multi-region ENS instances can be achieved by establishing a management connection to the ACK Edge cluster API server through a public network or a leased line.
Constraints
All ENS instances in the same edge node pool must belong to the same virtual private cloud (VPC). Instances in different VPCs cannot share a node pool.
Integrations
ELB instances can expose a Kubernetes Service across multiple regions simultaneously. For details, see Use ELB instances to expose Services in multiple regions.
The CSI plug-in manages statically and dynamically provisioned ENS disk volumes. For details, see Use ENS disks.
Add ENS nodes
Prerequisites
Before you begin, make sure you have:
An ACK Edge cluster
ENS instances provisioned in the same VPC
Add nodes to the cluster
Create an edge node pool in the ACK Edge cluster. All ENS instances you add to this pool must belong to the same VPC.
Add the ENS instances to the edge node pool.