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. This topic describes how to manage Nacos configurations.
Create a configuration
To centrally manage and maintain the configurations in an application, you can extract application variables and parameters from the code and store them in the MSE Nacos configuration center. This improves the accuracy and consistency of the configurations, reduces the maintenance cost, and simplifies the maintenance operations of the configurations. For more information, see Create a configuration.
Synchronize configurations
You can synchronize configurations for an application in different environments, such as the development environment and the test environment, or in different regions. You can create multiple microservices namespaces, create a configuration in one of the microservices namespaces, and then synchronize the configuration to the other microservices namespaces. You can use one of the following methods to synchronize configurations. 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 increases, the number of configuration files increases. You can manage configuration files in the MSE console. You can view configuration details and query, edit, import, export, clone, and delete configurations. For more information, see Manage configurations.
View historical versions
You can view historical version records of the Nacos configuration file in the MSE console. If an issue, such as a sudden deterioration in system performance or a feature exception, occurs due to a configuration change, you can roll back the system to the normal state at the earliest opportunity. For more information, see View historical versions.
Query listening information
You can query the listening information in the MSE console to check whether the modified configuration is pushed to the instances that listen to the configuration. For more information, see Query listening information.
Compare configuration contents
You can compare the current configuration with other configurations. You can compare the configurations that correspond to different data IDs and group IDs for MSE instances or namespaces. For more information, see Compare configuration contents.
Encrypt configurations
MSE is integrated with Key Management Service (KMS) to allow you to encrypt and decrypt configurations. This helps reduce the risk of sensitive data leaks. For more information, see Configuration encryption.
Configure canary release
MSE instances support the canary release feature. If you enable the canary release feature for MSE instances, you can release configurations to a small percentage of nodes to verify the configurations before you officially release the configurations. This reduces the risks caused by configuration pushes. For more information, see Configure canary release.