Container Service for Kubernetes:Release notes for ACK Edge of Kubernetes 1.26 - Container Service for Kubernetes

ACK Edge is a cloud-managed solution for Container Service for Kubernetes (ACK) that enables collaborative cloud-edge computing. This topic describes the release notes for ACK Edge of Kubernetes 1.26.

What's new in this release

Cluster version: ACK Edge is updated to 1.26.3-aliyun.1.
Kubernetes core: Node Admission and Pod Admission are now supported. Kubernetes version names no longer include the edge suffix.
Edge node autonomy: The metadata cache path format now includes group.version. Image repositories can be configured for system components.
Cloud-edge O&M channel: The Raven component is released for cross-region O&M communication. Proxy mode gateways now support high availability, auto scaling, and dynamic configuration.
Cell-based management: The YurtAppSet component manages workloads across multiple regions, with support for canary release by region.
Adding edge nodes: The node onboarding process is updated. edgehub is now deployed as a systemd service, and Red Hat Enterprise Linux 8.8 is supported.

Updated features

Cluster version

ACK Edge is updated to version 1.26.3-aliyun.1.

Kubernetes core

Version naming: The Kubernetes version name no longer includes the edge suffix and now aligns with the ACK version name.
Node Admission: Nodes cannot be moved between node pools by updating node labels. Labels for node pools in host network mode can be added to nodes.
Pod Admission: Affinity configurations can be added to pods to prevent pods with hostNetwork: false from being scheduled to node pools in host network mode.

Edge node autonomy

Metadata cache path: The group.version parameter is added to the metadata cache path. The path format changes from /etc/kubernetes/cache/{component}/{resource}/{ns}/{name} to /etc/kubernetes/cache/{component}/{group.version.resource}/{ns}/{name}.
Image repositories: Image repositories can now be configured for system components on edge nodes.

Cloud-edge O&M channel

Raven component: Raven is released for cross-region O&M communication. It manages cloud-edge O&M channels and monitors host and container metrics. For details, see raven-agent-ds.
Proxy mode gateways: Cloud and on-premises gateways in proxy mode now support high availability, auto scaling, and dynamic configuration.
Tunnel mode: Container metrics can be monitored in tunnel mode.
Internet access: Cloud gateways can be exposed to the Internet through Server Load Balancer (SLB) instances. Access Control Lists (ACLs) are supported for secure Internet access.

Cell-based management

YurtAppSet manages the same Deployments distributed across multiple regions from a single control point. It supports release, deletion, update, rollback, and scaling, and supports canary release based on regions.

Adding edge nodes

The following changes are made to the process for adding edge nodes:

edgehub deployment: edgehub is now deployed as a systemd service instead of a static pod.
kubelet configuration: The kubelet configuration file manages kubelet startup parameters.
Image repository source: The source of image repositories for system components on nodes can be specified. Both Internet and internal network access are supported.
Public IP addresses: The public IP addresses used when adding nodes are updated.
Operating system support: Red Hat Enterprise Linux 8.8 is now supported.
Parameter updates: The parameters for adding edge nodes are updated. For details, see the Parameters section of the "Add an edge node" topic.