MSE microservice administration leverages microservice namespaces to segregate resources and configurations across different environments. This topic describes the organization of microservices in MSE using microservice namespaces and the management thereof.
What is a microservice namespace
Typically, production, test, and development environments are established, each with resources isolated from the others. In MSE microservice administration, governance configurations for applications in different microservice namespaces are independent and strictly isolated, not affecting other namespaces. Thus, the same microservice application has separate governance configurations when deployed in different environments. Microservice namespaces are used to isolate applications across these environments.
Microservice namespaces are distinct from Kubernetes namespaces. When connecting an application, you can designate the namespace it connects to in MSE by setting the label mseNamespace: ${namespace name} on the pod or the corresponding Kubernetes namespace.
What is an application in MSE microservice administration
A microservice application is a Java process that provides a suite of microservices. It encapsulates the cohesive business logic of microservices and is supported by dedicated maintenance and development engineers.
In terms of deployment mode, an MSE microservice administration application corresponds to a set of deployments.
When connecting an application, if you add the labels mseNamespace: prod and msePilotCreateAppName: ${application name} to the pod, the application will connect to the corresponding application in the prod microservice namespace. Application names must not exceed 63 characters.
Scenarios
Environment management: Isolate each environment and its resources by distinguishing between production (Prod), test (Test), and development (Dev) environments.
Resource isolation: Within each environment, governance configurations for applications in different microservice namespaces are strictly isolated and do not affect other namespaces.
Example 1:
In practice, you can connect all applications in the test environment to the microservice namespace
test(e.g.,test/example-app) and all applications in the production environment to the microservice namespaceprod(e.g.,prod/example-app). When utilizing MSE microservice administration features, you can configure and authenticate on thetest/example-appapplication. Once authentication is successful, return to theprod/example-appapplication to set the same features.NoteWe recommend using separate databases, Message Queue clusters, Kubernetes clusters, and Nacos instances for different microservice namespaces to prevent changes in the test environment from impacting the production environment and to ensure stability.
Example 2:
If you have three environments within the same VPC for application development, testing, and production, you can create a microservice namespace for each environment (e.g., Dev, Test, and Prod). Create clusters and deploy applications within these microservice namespaces. Applications in one namespace are isolated from those in other namespaces.
Microservice namespace version description
Microservice administration is available in both Professional and Enterprise Editions, each with distinct features and pricing. For Enterprise Edition users, not all applications require runtime protection capabilities, such as those in the Dev environment. You can downgrade some namespaces to Professional Edition as needed, while others, like those in the Prod environment, default to Enterprise Edition to accommodate the needs of different environments accessing MSE.
For more information about the billing details of microservice administration, see Billing Overview of Microservice Administration.
Usage of microservice namespaces
Create a microservice namespace
Log on to the MSE console.
In the left-side navigation pane, select Microservices Governance> O&M Center.
On the Operation Center page, click the name of the Kubernetes cluster you want to access.
On the Cluster Details page, click the corresponding Microservice Namespace under the Operation column.
In the dialog box for the corresponding microservice namespace, enter the name and then click OK.
What to do next
Access MSE Administration Center for ACK and ACS Microservice Applications (Java Version)
Access MSE Administration Center for ACK Microservice Applications (Golang Version)
Quickly Experience Service Administration Capabilities in 15 Minutes (Java Version)
Quickly Experience Service Administration Capabilities in 15 Minutes (Golang Version)