If your Microservices Engine (MSE) Nacos instance serves as a configuration center, you can manage the configuration files of the Nacos instance in the MSE console.
Create a configuration
Extract application variables and parameters from code and store them in the MSE Nacos configuration center to centrally manage configurations. This improves configuration accuracy and consistency, reduces maintenance costs, and simplifies maintenance operations. For more information, see Create a configuration.
Synchronize configurations
You can synchronize configurations across environments, such as development and test environments, or across regions. Create multiple microservices namespaces, add a configuration to one namespace, and then synchronize it to the others. The following synchronization methods are supported. For more information, see Synchronize configurations.
-
Synchronize configurations among namespaces in the same region.
-
Synchronize configurations among namespaces that reside in different regions.
Manage configurations
As the number of microservice application instances grows, so does the number of configuration files. The MSE console allows you to view configuration details and query, edit, import, export, clone, and delete configurations. For more information, see Manage configurations.
View historical versions
View the version history of Nacos configuration files in the MSE console. If a configuration change causes issues such as performance degradation or feature exceptions, you can roll back to a previous version. For more information, see View historical versions.
Listener queries
Query listener information in the MSE console to verify whether updated configurations have been pushed to the subscribing instances. For more information, see Query listening information.
Query push tracks
After you modify a configuration, check the push track to verify that the configuration is delivered. For more information, see Query push tracks.
Compare configuration contents
Compare the current configuration with configurations that use different data IDs or group IDs across MSE instances or namespaces. For more information, see Compare configuration contents.
Encrypt configurations
MSE integrates with Key Management Service (KMS) to encrypt and decrypt configurations, reducing the risk of sensitive data leaks. For more information, see Configuration encryption.
Configure canary release
MSE instances support canary release, which lets you push configurations to a small subset of nodes for verification before a full rollout. This reduces the risk of configuration-related issues. For more information, see Configure a phased release.