summaryrefslogtreecommitdiff
path: root/CHANGELOG
diff options
context:
space:
mode:
authorShelley-BaoYue <baoyue2@huawei.com>2022-09-27 20:43:21 +0800
committerShelley-BaoYue <baoyue2@huawei.com>2022-09-27 20:43:21 +0800
commita98724bb5692a61b304b8adc10fd64b91d0544fa (patch)
tree58ca113b20804c4279b2c21a90a437b043c7694e /CHANGELOG
parentMerge pull request #4234 from gy95/role (diff)
downloadkubeedge-a98724bb5692a61b304b8adc10fd64b91d0544fa.tar.gz
update changelog for 1.12.0
Signed-off-by: Shelley-BaoYue <baoyue2@huawei.com>
Diffstat (limited to 'CHANGELOG')
-rw-r--r--CHANGELOG/CHANGELOG-1.12.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/CHANGELOG/CHANGELOG-1.12.md b/CHANGELOG/CHANGELOG-1.12.md
index ee0afebf0..d7ced7957 100644
--- a/CHANGELOG/CHANGELOG-1.12.md
+++ b/CHANGELOG/CHANGELOG-1.12.md
@@ -81,6 +81,7 @@ Refer to the links for more details.
## Important Steps before Upgrading
+- If you want to upgrade KubeEdge to v1.12, the configuration file in EdgeCore has upgraded to v1alpha2, you must modify your configuration file of edged in EdgeCore to adapt the new edged.
- If you want to use authorization for Edge Kube-API Endpoint, please enabled `RequireAuthorization` feature through feature gate both in CloudCore and EdgeCore.
If `RequireAuthorization` feature is enabled, metaServer will only serve for https request.
- If you want to upgrade edgemesh to v1.12, you do not need to deploy the existing edgemesh-server, and you need to configure relayNodes.