From 8a2fb89df37192f40330644239be4c0e6db4b196 Mon Sep 17 00:00:00 2001 From: Rory Z <16801068+Rory-Z@users.noreply.github.com> Date: Tue, 24 Sep 2024 15:59:10 +0800 Subject: [PATCH] chore: dump version to 2.2.24 Signed-off-by: Rory Z <16801068+Rory-Z@users.noreply.github.com> --- RELEASE.md | 8 ++++---- docs/en_US/tasks/configure-emqx-core-replicant.md | 4 ++++ docs/zh_CN/tasks/configure-emqx-core-replicant.md | 4 ++++ 3 files changed, 12 insertions(+), 4 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index d240a853..d8aad1f9 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -1,6 +1,6 @@ # Release Note 🍻 -EMQX Operator 2.2.23 has been released. +EMQX Operator 2.2.24 has been released. ## Supported version + apps.emqx.io/v2beta1 @@ -13,11 +13,11 @@ EMQX Operator 2.2.23 has been released. + EMQX at 4.4.14 and later + EMQX Enterprise at 4.4.14 and later -## Other Changes ✨ +## Enhancements 🚀 + `apps.emqx.io/v2beta1 EMQX`. - + Delete `apps.emqx.io/v2beta1/EMQX/status.coreNodes[*].uptime` and `apps.emqx.io/v2beta1/EMQX/status.replicantNodes[*].uptime`, because EMQX operator will constantly updating them. This is unnecessary wear and tear. + + Fix sometimes cannot update EMQX's configuration when EMQX is running. ## How to install/upgrade EMQX Operator 💡 @@ -29,7 +29,7 @@ helm repo update helm upgrade --install emqx-operator emqx/emqx-operator \ --namespace emqx-operator-system \ --create-namespace \ - --version 2.2.23 + --version 2.2.24 kubectl wait --for=condition=Ready pods -l "control-plane=controller-manager" -n emqx-operator-system ``` diff --git a/docs/en_US/tasks/configure-emqx-core-replicant.md b/docs/en_US/tasks/configure-emqx-core-replicant.md index bf936261..d9046a1a 100644 --- a/docs/en_US/tasks/configure-emqx-core-replicant.md +++ b/docs/en_US/tasks/configure-emqx-core-replicant.md @@ -7,6 +7,10 @@ ## Core Nodes And Replicant Nodes +:::tip +Just EMQX Enterprise Edition supports Core + Replicant cluster. +::: + In EMQX 5.0, the nodes in the EMQX cluster can be divided into two roles: core (Core) node and replication (Replicant) node. The Core node is responsible for all write operations in the cluster, which is consistent with the behavior of the nodes in the EMQX 4.x cluster, and serves as the real data source of the EMQX database [Mria](https://github.com/emqx/mria) to store the routing table, Data such as sessions, configurations, alarms, and Dashboard user information. The Replicant node is designed to be stateless and does not participate in the writing of data. Adding or deleting Replicant nodes will not change the redundancy of the cluster data. For more information about the EMQX 5.0 architecture, please refer to the document: [EMQX 5.0 Architecture](https://docs.emqx.com/en/enterprise/v5.0/deploy/cluster/mria-introduction.html), the topological structure of the Core node and the Replicant node is shown in the following figure:
diff --git a/docs/zh_CN/tasks/configure-emqx-core-replicant.md b/docs/zh_CN/tasks/configure-emqx-core-replicant.md index 56b35a9d..ac3ee6e3 100644 --- a/docs/zh_CN/tasks/configure-emqx-core-replicant.md +++ b/docs/zh_CN/tasks/configure-emqx-core-replicant.md @@ -7,6 +7,10 @@ ## Core 节点与 Replicant 节点 +::: tip +仅有 EMQX 企业版支持 Core + Replicant 节点集群。 +::: + 在 EMQX 5.0 中，EMQX 集群中的节点可以分成两个角色：核心（Core）节点和 复制（Replicant）节点。Core 节点负责集群中所有的写操作，与 EMQX 4.x 集群中的节点行为一致，作为 EMQX 数据库 [Mria](https://github.com/emqx/mria) 的真实数据源来存储路由表、会话、配置、报警以及 Dashboard 用户信息等数据。而 Replicant 节点被设计成无状态的，不参与数据的写入，添加或者删除 Replicant 节点不会改变集群数据的冗余。更多关于 EMQX 5.0 架构的信息请参考文档：[EMQX 5.0 架构](https://docs.emqx.com/zh/enterprise/v5.0/deploy/cluster/mria-introduction.html#mria-%E6%9E%B6%E6%9E%84%E4%BB%8B%E7%BB%8D)，Core 节点与 Replicant 节点的拓扑结构如下图所示：