1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
|
* [v1.13.1](#v1131)
* [Downloads for v1.13.1](#downloads-for-v1131)
* [KubeEdge v1.13.1 Release Notes](#kubeedge-v1131-release-notes)
* [Changelog since v1.13.0](#changelog-since-v1130)
* [Important Steps before Upgrading](#important-steps-before-upgrading-for-1131)
* [v1.13.0](#v1130)
* [Downloads for v1.13.0](#downloads-for-v1130)
* [KubeEdge v1.13 Release Notes](#kubeedge-v113-release-notes)
* [1.13 What's New](#113-whats-new)
* [Important Steps before Upgrading](#important-steps-before-upgrading)
* [Other Notable Changes](#other-notable-changes)
* [Bug Fixes](#bug-fixes)
# v1.13.1
## Downloads for v1.13.1
Download v1.13.1 in the [v1.13.1 release page](https://github.com/kubeedge/kubeedge/releases/tag/v1.13.1).
## KubeEdge v1.13.1 Release Notes
### Changelog since v1.13.0
- Fix MQTT container exited abnormally when edgecore using cri runtime. ([#4875](https://github.com/kubeedge/kubeedge/pull/4875), [@Shelley-BaoYue](https://github.com/Shelley-BaoYue))
- Deal with error in delete pod upstream msg. ([#4878](https://github.com/kubeedge/kubeedge/pull/4878), [@Shelley-BaoYue](https://github.com/Shelley-BaoYue))
- Update pod db when patch pod successfully. ([#4891](https://github.com/kubeedge/kubeedge/pull/4891), [@Shelley-BaoYue](https://github.com/Shelley-BaoYue))
- Use nodeIP initialization in Kubelet, support reporting nodeIP dynamically . ([#4894](https://github.com/kubeedge/kubeedge/pull/4894), [@Shelley-BaoYue](https://github.com/Shelley-BaoYue))
- Fix delete statefulset pod failed. ([#4873](https://github.com/kubeedge/kubeedge/pull/4873), [@Shelley-BaoYue](https://github.com/Shelley-BaoYue))
- Fix container terminated when edgecore restart. ([#4870](https://github.com/kubeedge/kubeedge/pull/4870), [@Shelley-BaoYue](https://github.com/Shelley-BaoYue))
- Fix iptables-manager and controller-manager image name. ([#4620](https://github.com/kubeedge/kubeedge/pull/4620), [@gy95](https://github.com/gy95))
- Wait for cache sync when cloudcore reboot. ([#4620](https://github.com/kubeedge/kubeedge/pull/4786), [@vincentgoat](https://github.com/vincentgoat))
### Important Steps before Upgrading for 1.13.1
- In previous versions, when edge node uses remote runtime (not docker runtime), using `keadm join` and specifying `--with-mqtt=true` to install edgecore will cause the Mosquitto container exits abnormally. In this release, this problem has been fixed. Users can specify `--with-mqtt=true` to start Mosquitto container when installing edgecore with `keadm join`.
# v1.13.0
## Downloads for v1.13.0
Download v1.13.0 in the [v1.13.0 release page](https://github.com/kubeedge/kubeedge/releases/tag/v1.13.0).
## KubeEdge v1.13 Release Notes
## 1.13 What's New
### Performance Improvement
- **CloudCore memory usage is reduced by 40%**, through unified generic Informer and reduce unnecessary cache. ([#4375](https://github.com/kubeedge/kubeedge/pull/4375)) ([#4377](https://github.com/kubeedge/kubeedge/pull/4377))
- List-watch dynamicController processing optimization, each watcher has a separate channel and goroutine processing to improve processing efficiency ([#4506](https://github.com/kubeedge/kubeedge/pull/4506))
- Added list-watch synchronization mechanism between cloud and edge and add dynamicController watch gc mechanism ([#4484](https://github.com/kubeedge/kubeedge/pull/4484))
- Removed 10s hard delay when offline nodes turn online ([#4490](https://github.com/kubeedge/kubeedge/pull/4490))
- Added prometheus monitor server and a metric connected_nodes to cloudHub. This metric tallies the number of connected nodes each cloudhub instance ([#3646](https://github.com/kubeedge/kubeedge/pull/3646))
- Added pprof for visualization and analysis of profiling data ([#3646](https://github.com/kubeedge/kubeedge/pull/3646))
- CloudCore configuration is now automatically adjusted according to nodeLimit to adapt to the number of nodes of different scales ([#4376](https://github.com/kubeedge/kubeedge/pull/4376))
### Security Improvement
- KubeEdge is proud to announce that we are digitally signing all release artifacts (including binary artifacts and container images).
Signing artifacts provides end users a chance to verify the integrity of the downloaded resource. It allows to mitigate man-in-the-middle attacks
directly on the client side and therefore ensures the trustfulness of the remote serving the artifacts. By doing this, we reached the
SLSA security assessment level L3 ([#4285](https://github.com/kubeedge/kubeedge/pull/4285))
- Remove the token field in the edge node configuration file edgecore.yaml to eliminate the risk of edge information leakage ([#4488](https://github.com/kubeedge/kubeedge/pull/4488))
### Upgrade Kubernetes Dependency to v1.23.15
Upgrade the vendered kubernetes version to v1.23.15, users are now able to use the feature of new version on the cloud and on the edge side.
Refer to the link for more details. ([#4509](https://github.com/kubeedge/kubeedge/pull/4509))
### Modbus Mapper based on DMI
Modbus Device Mapper based on DMI is provided, which is used to access Modbus protocol
devices and uses DMI to synchronize the management plane messages of devices with edgecore.
Refer to the link for more details. ([mappers-go#79](https://github.com/kubeedge/mappers-go/pull/79))
### Support Rolling Upgrade for Edge Nodes from Cloud
Users now able to trigger rolling upgrade for edge nodes from cloud, and specify number of concurrent upgrade nodes with `nodeupgradejob.spec.concurrency`.
The default Concurrency value is 1, which means upgrade edge nodes one by one.
Refer to the link for more details. ([#4476](https://github.com/kubeedge/kubeedge/pull/4476))
### Test Runner for conformance test
KubeEdge has provided the runner of the conformance test, which contains the scripts
and related files of the conformance test.
Refer to the link for more details. ([#4411](https://github.com/kubeedge/kubeedge/pull/4411))
### EdgeMesh: Added configurable field TunnelLimitConfig to edge-tunnel module
The tunnel stream of the edge-tunnel module is used to manage the data stream state of the tunnel.
Users can obtain a stable and configurable tunnel stream to ensure the reliability of user application traffic forwarding.
Users can configure the cache size of tunnel stream according to `TunnelLimitConfig` to support larger application relay traffic.
Refer to the link for more details. ([#399](https://github.com/kubeedge/edgemesh/pull/399))
Cancel the restrictions on the relay to ensure the stability of the user's streaming application or long link application.
Refer to the link for more details. ([#400](https://github.com/kubeedge/edgemesh/pull/400))
## Important Steps before Upgrading
- EdgeCore now uses `containerd` runtime by default on KubeEdge v1.13. If you want to use `docker` runtime, you
must set `edged.containerRuntime=docker` and corresponding docker configuration like `DockerEndpoint`, `RemoteRuntimeEndpoint` and `RemoteImageEndpoint` in EdgeCore.
|
