Container Service for Kubernetes:(Discontinued) ACK Edge Kubernetes 1.22 release notes

Cluster version

Kubernetes core

• kube-apiserver can now use an Express Connect circuit to access on-premises servers added to the cluster, including pods running on those servers.

• The kube-controller-manager, kube-apiserver, and ack-scheduler parameters in an ACK Edge Pro cluster are now configurable.

Edge node autonomy

Stability improvements for edge node autonomy management components:

• RESTful APIs for over-the-air (OTA) updates are now supported.

• The data filtering framework on the edge is optimized.

• Non-resource requests can now be forwarded and cached.

Cloud-edge O&M channel

Edge nodes are now grouped into edge node pools, which simplifies node and network connection management. Each edge node pool connects to the cloud over either the Internet or an Express Connect circuit, and traffic is routed accordingly:

• Internet-connected pools: Requests are sent through the cloud-edge tunnel, which acts as a forward proxy.

• Express Connect-connected pools: Requests go directly to the node ports in the edge node pool. For example, kubectl exec and kubectl logs are sent to port 10250 and port 10255 on edge nodes.

DNS records are updated dynamically based on whether tunnel-agent is deployed. Edge node pools that connect over an Express Connect circuit do not require tunnel-agent.

Cell-based management

The API version of the CustomResourceDefinition (CRD) used for edge node pool management and cell-based management is updated to apiextensions.k8s.io/v1.