Add release note for v1.13.

>
>
Co-authored-by: gy95 <1015105054@qq.com>
Co-authored-by: vincentgoat <linguohui1@huawei.com>
Co-authored-by: wackxu <xushiwei5@huawei.com>
Co-authored-by: Shelley-BaoYue <baoyue2@huawei.com>
Co-authored-by: Poorunga <2744323@qq.com>
Co-authored-by: RyanZhaoXB <zhaoran11@huawei.com>

Signed-off-by: fisherxu <xufei40@huawei.com>

2 files changed, 92 insertions, 0 deletions

diff --git a/CHANGELOG/CHANGELOG-1.13.md b/CHANGELOG/CHANGELOG-1.13.md
new file mode 100644
index 000000000..97c9a3993
--- /dev/null
+++ b/CHANGELOG/CHANGELOG-1.13.md
@@ -0,0 +1,91 @@
+
+* [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.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
+
+- Add 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))
+- Add pprof for visualization and analysis of profiling data ([#3646](https://github.com/kubeedge/kubeedge/pull/3646))
+- CloudCore configuration is automatically adjusted according to nodeLimit to adapt to the number of nodes of different scales ([#4376](https://github.com/kubeedge/kubeedge/pull/4376))
+- CloudCore memory usage optimization. Through unified generic Informer and reduce unnecessary cache, memory usage is reduced by 40% ([#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))
+- fix 10s delay for edge request when the node is offline ([#4490](https://github.com/kubeedge/kubeedge/pull/4490))
+- Added list-watch synchronization mechanism between cloud and edge and add dynamicController watch gc mechanism ([#4484](https://github.com/kubeedge/kubeedge/pull/4484))
+
+
+### 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
+
+Upgrade the vendered kubernetes version to v1.23.15,users now can use the feature of new version on the cloud and on the edge side.
+
+Refer to the links 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 links for more details.
+([mappers-go#79](https://github.com/kubeedge/mappers-go/pull/79))
+
+
+### Support Setting Concurrent Count for Edge Node Upgrade from Cloud
+
+
+Support upgrading nodes one by one, but not upgrade them all once a time. Concurrency specifies the max number of edge nodes that can be upgraded at the same time. 
+The default Concurrency value is 1. So that we can upgrade edge nodes one by one.
+Refer to the links for more details.
+([#4476](https://github.com/kubeedge/kubeedge/pull/4476))
+
+### Test Runner
+
+KubeEdge has provided the runner of the conformance test, which contains the scripts 
+and related files of the conformance test. 
+Follow the [instructions.md](https://github.com/kubeedge/community/pull/130/files#diff-1d40b792672f83aebb7d935e70885b4a3ee0cb612f1b7ce56c96da42676b928bR1) perform a conformance test ([#4411](https://github.com/kubeedge/kubeedge/pull/4411))
+
+### EdgeMesh —— Added configurable field TunnelLimitConfig to edge-tunnel module @jiezhang
+
+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 links 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 links for more details.
+([#400](https://github.com/kubeedge/edgemesh/pull/400))
+
+
+
+## Important Steps before Upgrading
+
+- EdgeCore 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.
diff --git a/CHANGELOG/README.md b/CHANGELOG/README.md
index fb0495ac7..2da8e9f64 100644
--- a/CHANGELOG/README.md
+++ b/CHANGELOG/README.md
@@ -1,5 +1,6 @@
 # CHANGELOGs
 
+- [CHANGELOG-1.13.md](./CHANGELOG-1.13.md)
 - [CHANGELOG-1.12.md](./CHANGELOG-1.12.md)
 - [CHANGELOG-1.11.md](./CHANGELOG-1.11.md)
 - [CHANGELOG-1.10.md](./CHANGELOG-1.10.md)