All Products
Search

This Product

    Container Service for Kubernetes:Use the Terway Edge network plugin with ENS elastic network interfaces

    Document Center

    Container Service for Kubernetes:Use the Terway Edge network plugin with ENS elastic network interfaces

    Last Updated:Sep 29, 2026

    Terway Edge is the underlay network plugin for Container Service for Kubernetes (ACK) Edge clusters. It assigns Elastic Network Interfaces (ENIs) from Edge Node Service (ENS) directly to pods for container communication.

    How it works

    image

    Terway Edge supports two deployment zones, each using the same ENI-based pod IP allocation model:

    • Virtual Private Cloud (VPC) — Terway assigns ENIs to pods. Multiple pods share a single ENI, and pod IPs are allocated from the ENI's private IP addresses. The pod network and Elastic Compute Service (ECS) instances reside on the same network plane.

    • Edge-side ENS network — Terway assigns ENIs of ENS to pods. Multiple pods share a single ENI, and pod IPs are allocated from the ENI's private IP addresses. The pod network and ENS instances reside on the same network plane.

    Traffic between the central VPC and the edge ENS network is routed through Edge Network Acceleration (ENA), which provides seamless connectivity between containers and hosts across network domains.

    Important

    Do not manually configure private IP addresses. Terway Edge automatically assigns ENIs and their attached private IP addresses to pods.

    Prerequisites

    Before you begin, ensure that you have:

    • Selected Terway-edge as the Network Plug-in when creating an Edge cluster. For more information, see Use Terway Edge.

    • Installed the terway-edge-controlplane component. For more information, see Component management.

    Step 1: Bind an ENI

    Bind an ENI to the ENS instance before adding the node to the cluster. Each ENI supports up to 25 private IP addresses, with each address assigned to one pod. The maximum pod capacity per ENS instance equals the number of bound ENIs multiplied by 25 — bind additional ENIs as needed to meet your pod capacity requirements.

    1. Log on to the ENS console. In the left-side navigation pane, choose Network Management > ENIs.

    2. On the ENIs page, click Create ENI. Configure the parameters based on your requirements and click Create.

    3. Stop the ENS instance before proceeding. Binding an ENI requires the instance to be in a stopped state.

      Important

      If the ENS instance is running, stop it before you bind the ENI. After binding, restart the instance to apply the changes.

    4. Find the ENI you just created. In the Actions column, click Associate Resource, select the appropriate Instance ID/Name, and click OK.

    Step 2: Add the ENS node

    Add the ENS node to the ACK Edge cluster. For more information, see Add an edge node.