All Products
Search

This Product

    Container Service for Kubernetes:[Discontinued] Release notes on ACK Edge of Kubernetes 1.16

    Document Center

    Container Service for Kubernetes:[Discontinued] Release notes on ACK Edge of Kubernetes 1.16

    Last Updated:Mar 27, 2026

    ACK Edge is a cloud-managed solution provided by Container Service for Kubernetes (ACK) for collaborative cloud-edge computing. This topic lists the changes to ACK Edge of Kubernetes 1.16.

    What's changed

    Area

    Change types

    Summary

    Kubernetes core

    Fixed, Added

    kubelet startup fix; IPVS mode support; NIC-based IP configuration

    Edge node autonomy

    Breaking, Added

    Certificate directory and filenames changed; Prometheus metrics added

    Cloud-edge tunnels

    Breaking, Upgraded, Added

    Protocol changed from TCP to gRPC; automatic certificate management

    Monitor components

    Upgraded, Added

    Metrics Server upgraded from V0.2.1 to V0.3.8; Cloud Monitor token support

    Cell-based management

    Added

    New yurt-app-manager component; node pool and UnitedDeployment support

    Container runtimes

    Upgraded, Changed

    runc upgraded to 1.0.0-rc10; cgroup driver changed to systemd

    CNI plug-in

    Fixed

    Pod IP collision fix across namespaces

    Adding edge nodes

    Added

    CIDR conflict check; configurable IP count; new parameters; Ubuntu + Linux kernel 5.4 support

    API changes

    Added

    Node pool API operations for edge node pools

    Kubernetes core

    Fixed: kubelet no longer fails to start when the cpuacct.stat file on a node contains more than four records.

    Added:

    • kube-proxy now supports IP Virtual Server (IPVS) mode.

    • kubelet can configure a node's internal IP address by specifying the name of a network interface controller (NIC).

    For more information, see (Discontinued) Kubernetes 1.16 release notes.

    Autonomy of edge nodes

    Important

    This release includes breaking changes to the edge-hub certificate path and filenames. Update your configurations before upgrading.

    Breaking changes:

    • The certificate directory for edge-hub has moved from /etc/kubernetes/edge-hub to /var/lib/edge-hub. Update any scripts or configurations that reference the old path.

    • The following certificate files have been renamed:

      Old filename

      New filename

      edge-hub.kubeconfig

      edge-hub.conf

      bootstrap-edge-hub-current.conf

      bootstrap-hub.conf

    Added:

    • When cached data is lost, clients now receive HTTP status code 404 instead of an empty string.

    • A Prometheus metrics interface has been added to edge-hub.

    • iptables notrack has been added for IP addresses 127.0.0.1:10261 and 169.254.2.1:10261, improving iptables performance.

    For more information, see Network autonomy of edge nodes.

    Cloud-edge tunnels

    Important

    The tunnel protocol has changed from TCP to gRPC, and the edge-tunnel-agent Pod label has also changed. Review the breaking changes below before upgrading.

    Breaking changes:

    • The tunnel communication protocol has changed from standard TCP to gRPC. Data transmitted over gRPC tunnels is 40% smaller than over TCP.

    • The label used to deploy the edge-tunnel-agent Pod has changed to alibabacloud.com/is-edge-worker: "true".

    Upgraded:

    • edge-tunnel-agent can now automatically request and renew certificates, decoupling it from node certificates. Certificates are stored in /var/lib/edge-tunnel-agent/pki.

    Added:

    • Prometheus metrics have been added to edge-tunnel-agent.

    For more information, see Overview of the cloud-edge O&M communication component Tunnel.

    Monitor components

    Upgraded: Metrics Server has been upgraded from V0.2.1 to V0.3.8.

    Added: ACK Edge can now connect to Cloud Monitor using tokens.

    Cell-based management at the edge

    A new component, yurt-app-manager, has been introduced to support cell-based management at the edge. This release adds:

    • Node management by node pool.

    • Application management using the UnitedDeployment controller.

    • Service topology configuration to expose a Service only to the node or node pool where it is deployed.

    For more information, see Overview of edge node pools.

    Container runtimes

    Upgraded: The runc version for Advanced RISC Machine (ARM) and ARM64 architectures has been upgraded to 1.0.0-rc10.

    Changed: The cgroup driver has changed from cgroupfs to systemd.

    CNI plug-in

    Fixed: The Container Network Interface (CNI) plug-in no longer allocates invalid IP addresses to Pods that share the same name across different namespaces.

    Add edge nodes to a cluster

    Added:

    • Classless Inter-Domain Routing (CIDR) conflict check is now performed when adding edge nodes.

    • The number of IP addresses assignable to a node is configurable.

    • The following parameters are now supported: labels, nodeIface, annotations, and taints.

    • Ubuntu systems running Linux kernel 5.4 are now supported.

    For more information, see Add an edge node.

    API changes

    Node pool API operations can now be used to manage edge node pools. For more information, see Node pools.