chore: add known 6.0 issues

dir.yaml

@@ -1133,6 +1133,7 @@
       title_cn: 已知问题
       title_ja: 既知の問題
       children:
+        - changes/known-issues-6.0
         - changes/known-issues-5.9
         - changes/known-issues-5.8
         - changes/known-issues-5.3

en_US/changes/known-issues-5.8.md

@@ -2,18 +2,10 @@
 
 ## e5.8.8
 
-- **Disabling Message Transformation or Schema Validation has no effect after deleting a preceding item (since 5.8.0, will be fixed in 5.8.8)**.
-
-  If you delete a Message Transformation or Schema Validation entry and then disable any subsequent entry in the list, the entry remains enabled.
-
-  > **Workaround:**
-  > Run the following command on any EMQX node.
-  >
-  > ```
-  > $ emqx eval "begin ets:delete_all_objects(emqx_message_transformation_index), emqx_message_transformation_config:load() end."
-  > ```
-
-- **External Schema Registries are not loaded after a node restart (since 5.8.1, will be fixed in 5.8.8)**.
+| Since version | Issue                                                        | Workaround                                                   | Status         |
+| ------------- | ------------------------------------------------------------ | ------------------------------------------------------------ | -------------- |
+| 5.8.0         | **Disabling Message Transformation or Schema Validation has no effect after deleting a preceding item**<br />If you delete a Message Transformation or Schema Validation entry and then disable any subsequent entry in the list, the entry remains enabled. | Run the following command on any EMQX node:<br />`$ emqx eval "begin ets:delete_all_objects(emqx_message_transformation_index), emqx_message_transformation_config:load() end."` | Fixed in 5.8.8 |
+| 5.8.1         | **External Schema Registries are not loaded after a node restart** | None                                                         | Fixed in 5.8.8 |
 
 ## e5.8.6
 

en_US/changes/known-issues-6.0.md

@@ -0,0 +1,7 @@
+# Known Issues in EMQX 6.0
+
+## 6.0.0
+
+| Since version | Issue                                                        | Workaround                                                   | Status |
+| ------------- | ------------------------------------------------------------ | ------------------------------------------------------------ | ------ |
+| 6.0.0         | **Cannot perform rolling upgrade from cluster running 5.x to 6.0.0 when older bridges are in the configuration**<br />Clusters that have started running from older EMQX versions that contain the now deprecated `bridges` configuration root will fail to sync their configuration to the new 6.0 nodes, because the latter have dropped for such roots and thus fail to start the corresponding Connectors, Actions and Sources. | Starting from 6.0.1, an RPC call is made to the older node to upgrade the configuration to convert `bridges` into `connectors`, `sources` and `actions`, facilitating rolling upgrades with less manual invervention.<br />Alternatively, each affected bridge can be updated via HTTP API or CLI to induce a configuration update (e.g., change the description) which will also upgrade the persisted `cluster.hocon` file.<br />The following Connector/Sources/Actions might still require manual changes before attempting a rolling upgrade:<br /> - GCP PubSub Consumer<br /> - Kafka Consumer<br />If there are any such sources in the configuration that still contain the `topic_mapping` field, the field must be removed from config and then one "Source + Rule" pair must be created for each entry. |        |

ja_JP/changes/known-issues-6.0.md

@@ -0,0 +1,7 @@
+# Known Issues in EMQX 6.0
+
+## 6.0.0
+
+| Since version | Issue                                                        | Workaround                                                   | Status |
+| ------------- | ------------------------------------------------------------ | ------------------------------------------------------------ | ------ |
+| 6.0.0         | **Cannot perform rolling upgrade from cluster running 5.x to 6.0.0 when older bridges are in the configuration**<br />Clusters that have started running from older EMQX versions that contain the now deprecated `bridges` configuration root will fail to sync their configuration to the new 6.0 nodes, because the latter have dropped for such roots and thus fail to start the corresponding Connectors, Actions and Sources. | Starting from 6.0.1, an RPC call is made to the older node to upgrade the configuration to convert `bridges` into `connectors`, `sources` and `actions`, facilitating rolling upgrades with less manual invervention.<br />Alternatively, each affected bridge can be updated via HTTP API or CLI to induce a configuration update (e.g., change the description) which will also upgrade the persisted `cluster.hocon` file.<br />The following Connector/Sources/Actions might still require manual changes before attempting a rolling upgrade:<br /> - GCP PubSub Consumer<br /> - Kafka Consumer<br />If there are any such sources in the configuration that still contain the `topic_mapping` field, the field must be removed from config and then one "Source + Rule" pair must be created for each entry. |        |

zh_CN/changes/known-issues-5.8.md

@@ -2,18 +2,10 @@
 
 ## e5.8.8
 
-- **删除前置条目后，禁用消息转换或 Schema 验证不生效（自 5.8.0 起，将在 5.8.8 修复）。**
-
-  如果你删除了一条消息转换或 Schema 验证条目，然后再禁用列表中其后的任意条目，该条目仍会保持启用状态。
-
-  > **解决方法：**
-  > 在任意一个 EMQX 节点上执行以下命令。
-  >
-  > ```
-  > $ emqx eval "begin ets:delete_all_objects(emqx_message_transformation_index), emqx_message_transformation_config:load() end."
-  > ```
-
-- **节点重启后不会加载外部 Schema Registry（自 5.8.1 起，将在 5.8.8 修复）。**
+| 始于版本 | 问题描述                                                     | 解决方法                                                     | 状态              |
+| -------- | ------------------------------------------------------------ | ------------------------------------------------------------ | ----------------- |
+| 5.8.0    | **删除前置条目后，禁用消息转换或 Schema 验证不生效**<br />如果你删除了一条消息转换或 Schema 验证条目，然后再禁用列表中其后的任意条目，该条目仍会保持启用状态。 | 在任意一个 EMQX 节点上执行以下命令：<br />`$ emqx eval "begin ets:delete_all_objects(emqx_message_transformation_index), emqx_message_transformation_config:load() end."` | 已在 5.8.8 中修复 |
+| 5.8.1    | **节点重启后不会加载外部 Schema Registry**                   | -                                                            | 已在 5.8.8 中修复 |
 
 ## e5.8.6
 

zh_CN/changes/known-issues-6.0.md

@@ -0,0 +1,7 @@
+# EMQX 6.0 已知问题
+
+## 6.0.0
+
+| 始于版本 | 问题描述                                                     | 解决方法                                                     | 状态 |
+| -------- | ------------------------------------------------------------ | ------------------------------------------------------------ | ---- |
+| 6.0.0    | **当配置中包含旧版桥接（bridges）时，无法从运行 5.x 的集群滚动升级到 6.0.0**<br />如果集群是从较早版本的 EMQX 启动，并且配置中包含现已弃用的 `bridges` 配置根项，则无法将配置同步到新的 6.0 节点。因为 6.0 版本已移除对该配置根项的支持，导致无法启动相应的连接器（Connector)、动作（Action）和 Source。 | 从 6.0.1 起，系统会通过 RPC 调用旧节点，将配置中的 `bridges` 自动转换为 `connectors`、`sources` 和 `actions`，从而减少手动干预，实现平滑滚动升级。<br />或者，也可以通过 HTTP API 或 CLI 手动更新每个受影响的桥接配置（例如修改描述字段），以触发配置更新并升级持久化的 `cluster.hocon` 文件。<br />以下连接器、Source 或动作类型在尝试滚动升级前仍可能需要手动修改：<br />- GCP PubSub 消费者<br />- Kafka 消费者<br />如果这些配置中仍包含 `topic_mapping` 字段，需要手动从配置中移除，并为每个条目创建一个 “Source + 规则” 对。 |      |