Matthew comments

Results 30 comments of


                                            Matthew

Support gray release based on tags.

## 一、背景灰度能力是稳定性保障的重要手段之一，在之前的版本中，Nacos 提供了基于 IP 地址的灰度方式，用户在发布正式版本配置前，可以选择一些 IP 地址下发新配置进行验证，确认业务正常，观察期过后，选择全量发布，但现有基于 IP 的灰度发布方式存在显著缺陷： - **业务关联性弱**：IP地址仅反映网络基础设施信息，无法与环境或功能模块等业务属性直接关联，导致灰度节点筛选缺乏业务逻辑支撑。 - **动态环境适配差**：在K8s等容器化部署场景中，节点重启后 IP 地址可能动态变化，导致预先配置的灰度规则失效。为解决上述问题，本功能希望支持用户通过自定义标签（如`env=test`、`region=beijing`）为节点赋予语义化属性，实现基于业务逻辑的精准灰度控制。 ## 二、目标 - 支持开源版本 Nacos 基于标签进行灰度发布，增强 Nacos 的灰度体系。 ## 三、详细设计 ### 3.1 配置发布整体流程...

Support gray release based on tags.

> [@KiteSoar](https://github.com/KiteSoar) 大佬, 谘询一下这个有进一步的消息可以分享的吗？暂时无，目前挂起中

Optimize the default authentication plugin.

好滴，我有空尝试一下

The config data is still accessible and correct after the namespace which the config attach to be deleted. 删除namespace之后，相关的配置数据依然存在可用。

Currently, deleting a namespace does not delete the related data. If you want to prevent access to the corresponding data, you need to delete the corresponding data. I think the...

The config data is still accessible and correct after the namespace which the config attach to be deleted. 删除namespace之后，相关的配置数据依然存在可用。

> Thanks. received. But I think it should mentioned in some document. Now, it cannot be searched in the official formal document. > > [@KiteSoar](https://github.com/KiteSoar), can you share the formal...

Matthew

Support gray release based on tags.

Support gray release based on tags.

Optimize the default authentication plugin.

The config data is still accessible and correct after the namespace which the config attach to be deleted. 删除namespace之后，相关的配置数据依然存在可用。

The config data is still accessible and correct after the namespace which the config attach to be deleted. 删除namespace之后，相关的配置数据依然存在可用。

[DSIP-9][registry] add raft registration plugin

[#ISSUE12748]Increase the read timeout time

不支持用户设置超时时间

[Summer 2025] 支持Agent2Agent服务管理模块 / Support Agent2Agent protocol management module

nacos2.x版本集群中的节点leaderStatus状态都为0