All Products
Search

This Product

    Container Service for Kubernetes:Release notes for ACK Edge of Kubernetes 1.20

    Document Center

    Container Service for Kubernetes:Release notes for ACK Edge of Kubernetes 1.20

    Last Updated:Oct 19, 2023

    ACK Edge is a cloud-managed solution provided by Container Service for Kubernetes (ACK). You can use ACK Edge to achieve collaborative cloud-edge computing. This topic describes the release notes for ACK Edge of Kubernetes 1.20.

    Autonomy of edge nodes

    The stability of components that are used to manage edge node autonomy is improved. The following section lists the major changes:

    • Health checks are enhanced: The issue that edge-hub keeps sending heartbeats after kubelet is stopped is fixed.

    • Management of node certificates is enhanced: If the edge-hub certificate is not deleted after a node is disconnected from a cluster, the edge-hub certificate is automatically updated after the node is connected to another cluster.

    • Traffic statistics on edge nodes are optimized: You can view traffic statistics about requests on edge nodes by accessing the endpoint of edge-hub: http://127.0.0.1:10267/metrics.

    • Stability is improved: The issue that a data race occurs when edge nodes process a large number of concurrent requests is fixed.

    Proxy for nodes in the cloud

    The cloud-hub component is available for nodes in the cloud. This component serves as a proxy to interact with the API server on behalf of other components in the cloud. The cloud-hub component supports Service Topology, which ensures that only CoreDNS is used to resolve domain names for requests from the cloud.

    Cloud-edge O&M channel

    The performance of cloud-edge O&M channels is optimized. The following section lists the major changes:

    • Request forwarding is improved:

      • Requests that are destined for {nodeName:Port} can be forwarded from the cloud to edge nodes.

      • Requests that are destined for the localhost endpoints on edge nodes can be forwarded from the cloud to edge nodes. This requires you to specify the localhost-proxy-ports field in the edge-tunnel-server-cfg ConfigMap.

    • The configurations related to ports other than ports 10250 and 10255 are optimized: You can specify HTTP ports in the http-proxy-ports field or specify HTTPS ports in the https-proxy-ports field of the edge-tunnel-server-cfg ConfigMap based on the type of the endpoint that is used by an edge node. The dnat-ports-pair field is retained. However, we recommend that you do not use dnat-ports-pair.

    • Certificate management is improved for edge-tunnel-server. When the IP address of the edge-tunnel-server-svc Service is changed, the tls server certificate of edge-tunnel-server is automatically updated. For example, the certificate is automatically updated when the edge-tunnel-server-svc Service is associated with a new Server Load Balancer (SLB) instance.

    Network plug-ins of containers

    The Flannel network plug-in is optimized. The following section lists the major changes:

    • Flannel is updated to v0.13.1.3-6838863-aliyun.

    • Flannel is optimized for intercommunication between the cloud and edge nodes when enhanced edge node pools are used or when the networks of the cloud and edge nodes are connected.

    CoreDNS

    CoreDNS is updated to v1.8.4. For more information, see CoreDNS.

    Container runtimes

    By default, containerd is used as the runtime and is updated to v1.4.8. For more information, see Release notes for containerd.

    Add edge nodes to a cluster

    The procedure for adding edge nodes to a cluster is optimized and new configurations are available. The new configurations allow you to connect Elastic Compute Service (ECS) instances to a cluster over an internal network. For more information, see Add an edge node.