Usage notes for edge-hub, release notes - Container Service for Kubernetes

The edge-hub component is a sidecar that runs as a static pod on each node. In edge-hub 0.12.0 and later, edge-hub runs as a systemd service when it is deployed in an edge node pool, and is named cloud-hub and runs as a DaemonSet when it is deployed in a node pool in the cloud. The DaemonSet ensures that each node in the node pool runs a pod of edge-hub. This topic introduces the edge-hub component and describes the usage notes and release notes for edge-hub.

Introduction

The edge-hub component serves as a proxy between the components at the edge and kube-apiserver in the cloud. The components at the edge include kubelet, kube-proxy, Flannel, and CoreDNS. You can deploy edge-hub at the edge or in the cloud. edge-hub that is deployed at the edge caches data received from the cloud. edge-hub that is deployed on the cloud is named cloud-hub.

edge-hub provides the following features:

Supports data caching. Application pods can retrieve cached data from edge-hub when they are restarted even if the edge is disconnected from the cloud. This prevents service interruptions.
Enables access to kube-apiserver. edge-hub serves as a proxy to allow pods to access kube-apiserver by using the inClusterConfig feature.
Selects routes based on the service topology. edge-hub automatically filters EndpointSlices to generate the service topology. Then, edge-hub can select routes based on the service topology to enable Services in the cluster to forward traffic only to backend pods in the same node pool.
Automatically changes image registries for system components. In scenarios where Express Connect circuits are used to connect to your cluster, private image registries are used to deploy system components. In scenarios where your cluster can access the Internet, public image registries are used to deploy system components.

手动开启edge-hub的数据缓存能力

Usage notes

For more information about how to use edge-hub, see Configure edge node autonomy and Run application pods that use InClusterConfig at the edge without making pod-facing changes.

Release notes

November 2023

Version

Image address

Description

Release date

Impact

v0.12.0

registry.cn-hangzhou.aliyuncs.com/acs/edge-hub:v0.12.0

This version is in canary release.

edge-hub can be deployed in ACK Edge clusters that run 1.26.3-aliyun.1.
The deployment mode of edge-hub is adjusted.
- edge-hub runs as a systemd service when it is deployed in an edge node pool.
- edge-hub runs as a DaemonSet and is named cloud-hub when it is deployed in a node pool in the cloud.

2023-11-28

No impact on workloads

August 2023

Version	Image address	Description	Release date	Impact
v0.11.0	registry.cn-hangzhou.aliyuncs.com/acs/edge-hub:v0.11.0	edge-hub can be deployed in ACK Edge clusters that run 1.24.6-aliyunedge.1.	2023-08-03	No impact on workloads

December 2022

Version	Image address	Description	Release date	Impact
v0.10.3	registry.cn-hangzhou.aliyuncs.com/acs/edge-hub:v0.10.3	edge-hub can be deployed in ACK Edge clusters that run 1.22-aliyunedge.1.	2022-12-07	No impact on workloads

January 2022

Version

Image address

Description

Release date

Impact

v0.10.0

registry.cn-hangzhou.aliyuncs.com/acs/edge-hub:v0.10.0

The first edge-hub version for ACK Edge clusters that run 1.20.11-aliyunedge.1 is released.

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 when the node is connected to another cluster.
Traffic statistics about 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.

2022-01-27

No impact on workloads

November 2021

Version	Image address	Description	Release date	Impact
v0.9.5	registry.cn-hangzhou.aliyuncs.com/acs/edge-hub:v0.9.5	The following issue is fixed: Edge requests that do not contain the Accept header are rejected.	2021-11-15	No impact on workloads
v0.9.4	registry.cn-hangzhou.aliyuncs.com/acs/edge-hub:v0.9.4	The following issue is fixed: The key usages of HTTPS server certificates are different in different programming languages.	2021-11-01	No impact on workloads

October 2021

Version	Image address	Description	Release date	Impact
v0.9.3	registry.cn-hangzhou.aliyuncs.com/acs/edge-hub:v0.9.3	The following issue is fixed: Large-sized data in data filters is truncated. Filtering can be disabled for requests from LoadBalancer Services.	2021-10-27	No impact on workloads
v0.9.2	registry.cn-hangzhou.aliyuncs.com/acs/edge-hub:v0.9.2	HTTPS servers are supported and port 10268 is added. The data filtering framework is supported at the edge.	2021-10-12	No impact on existing workloads. If you want to use the new features for existing workloads, recreate the pods.

September 2021

Version	Image address	Description	Release date	Impact
v0.9.1	registry.cn-hangzhou.aliyuncs.com/acs/edge-hub:v0.9.1	Edge nodes that run Windows are supported.	2021-09-23	No impact on workloads

July 2021

Version	Image address	Description	Release date	Impact
v0.9.0	registry.cn-hangzhou.aliyuncs.com/acs/edge-hub:v0.9.0	The first edge-hub version for ACK Edge clusters that run 1.18.8-aliyunedge.1 is released.	2021-07-12	No impact on workloads