All Products
Search

This Product

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

    Document Center

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

    Last Updated:Mar 26, 2026

    ACK Edge is the cloud-managed solution for cloud-edge collaborative computing in Container Service for Kubernetes (ACK). This topic covers the changes in ACK Edge for Kubernetes 1.20.

    Cluster version: 1.20.11-aliyunedge.1

    Deprecated in this release

    Important

    Review this section before upgrading. The following field has been deprecated.

    `dnat-ports-pair` in the `edge-tunnel-server-cfg` ConfigMap

    Use http-proxy-ports for HTTP endpoints or https-proxy-ports for HTTPS endpoints instead. The dnat-ports-pair field is retained for backward compatibility but is no longer recommended.

    Component versions

    Component Version Notes
    Flannel v0.13.1.3-6838863-aliyun
    CoreDNS v1.8.4
    containerd v1.4.8 Default container runtime

    What's new

    Edge node autonomy

    Bug fixes:

    • Fixed an issue where edge-hub continued sending heartbeats after kubelet stopped, causing incorrect health check results.

    • Fixed a data race that occurred when edge nodes processed large numbers of concurrent requests.

    Enhancements:

    • Automatic certificate management: If the edge-hub certificate is not deleted after a node disconnects from a cluster, the certificate is automatically updated when the node connects to a different cluster.

    • Traffic metrics endpoint: Access traffic statistics for requests on edge nodes at http://127.0.0.1:10267/metrics (served by edge-hub).

    Cloud node proxy

    The cloud-hub component is now available for nodes in the cloud. It acts as a proxy between other cloud-side components and the API server. cloud-hub supports Service Topology, ensuring that only CoreDNS resolves domain names for requests originating from the cloud.

    Cloud-edge O&M channel

    Request forwarding improvements:

    • Requests targeting {nodeName:Port} can now be forwarded from the cloud to edge nodes.

    • Requests targeting localhost endpoints on edge nodes can now be forwarded from the cloud. To enable this, configure the localhost-proxy-ports field in the edge-tunnel-server-cfg ConfigMap.

    Port configuration:

    Specify ports beyond 10250 and 10255 using the following fields in the edge-tunnel-server-cfg ConfigMap:

    Field Use for
    http-proxy-ports HTTP endpoints
    https-proxy-ports HTTPS endpoints

    TLS certificate auto-update:

    When the IP address of the edge-tunnel-server-svc service changes — for example, when the service is associated with a new Server Load Balancer (SLB) instance — the TLS server certificate of edge-tunnel-server is automatically updated.

    Adding edge nodes

    The procedure for adding edge nodes to a cluster is optimized with new configuration options, including support for connecting Elastic Compute Service (ECS) instances to a cluster over an internal network. For more information, see Add an edge node.

    Component release notes