Feature | Description |
Version of ACK Edge cluster | 1.22.15-aliyunedge.1 |
Kubernetes Core | The kube-apiserver component of an ACK edge cluster can use an Express Connect circuit to access on-premises servers that are added to the cluster and pods on the on-premises servers. The parameters of the kube-controller-manager, kube-apiserver, ack-scheduler components in ACK Edge Pro cluster can be configured.
|
Autonomy of edge nodes | The stability of components that are used to manage edge node autonomy is improved. The following section lists the updates: Restful APIs that support over-the-air (OTA) updates are supported. The data filtering framework on the edge is optimized. Non-resource requests can be forwarded and cached.
|
Cloud-edge O&M channel | Edge nodes are grouped into edge node pools to facilitate the management of nodes and network connections. Edge node pools can connect to the cloud over the Internet or an Express Connect circuit. Only requests destined for edge node pools that connect to the cloud over the Internet are sent to the cloud-edge tunnel that serves as a forward proxy. Requests destined for edge node pools that connect to the cloud over an Express Connect circuit are directly sent to the ports of the nodes in the edge node pools. For example, Kubernetes commands such as kubectl exec and kubectl logs are sent to port 10250 and port 10255 on edge nodes. DNS records are dynamically updated based on whether tunnel-agent is deployed. You do not need to deploy tunnel-agent in edge node pools that connect to the cloud over an Express Connect circuit. Requests from components in the cloud are sent to port 10263 of x-tunnel-server-internal-svc instead of port 10263 of x-tunnel-server-svc.
|
Cell-based management component | The API version of the CustomResourceDefinition (CRD) used to implement edge node pool management and cell-based management is updated to apiextensions.k8s.io/v1. |