DocsICP FilingConsole
Documentation
Home Page Microservices Engine User Guide Microservices governance System settings Disable MSE Microservices Governance

Disable MSE Microservices Governance

Updated at:
Copy as MD
Product
My Favorites

When you no longer need MSE Microservices Governance, disable it to prevent disruptions to your applications. This topic explains how.

Disable governance for a K8s cluster namespace

  1. Log on to the MSE console.

  2. In the left-side navigation pane, choose O&M Center, select the Kubernetes Clusters tab, and then click the name of the target cluster.

  3. In the Actions column for the target namespace, click Deactivate Microservice Governance.

Note

  • Disabling MSE Microservices Governance for a K8s cluster namespace does not affect applications within that namespace that were onboarded individually. To disable governance for these applications, follow the procedure for a single application described later in this topic.

  • After you disable MSE Microservices Governance for a K8s cluster namespace, you can still enable it for individual applications within that namespace.

  • Restart any applications already connected to MSE to complete disabling Microservices Governance.

Disable governance for a single Java application

  1. Log on to the ACK console.

  2. In the left-side navigation pane, click Clusters. Then, click the name of the cluster that you want to manage.

  3. In the left-side navigation pane, choose Workloads > Deployments.

  4. On the Deployments page, select a Namespace in the upper-left corner. Find the target application and choose More > Edit YAML in the Actions column.

  5. In the Edit YAML dialog box, find labels under spec > template > metadata. Delete msePilotAutoEnable: "on" or change it to msePilotAutoEnable: "off", and then click Update.

    labels:
  msePilotAutoEnable: "off"

Disable governance for an ECS instance

For a Java application deployed on an ECS instance and connected to MSE Microservices Governance through a Java Agent (the -javaagent startup parameter), you disable governance by modifying the application's startup parameters instead of using the ACK methods described earlier in this topic.

  1. Log on to the ECS instance and locate the startup script or configuration file of the Java application.

  2. In the startup parameters, perform one of the following operations:

    • (Recommended) Change -Dmse.enable=true to -Dmse.enable=false. This method does not affect ARMS.

    • Remove the -javaagent parameter. If the application is also connected to ARMS, this affects ARMS as well.

  3. Restart the Java application for the parameter change to take effect.

  4. Log on to the MSE console, and in the Applications, confirm that governance for the application is disabled or that the application no longer appears in the list.

Uninstall the MSE governance component from ACK

  1. Log on to the ACK console.

  2. In the left-side navigation pane, click Clusters. Then, click the name of the cluster that you want to manage.

  3. In the left-side navigation pane, choose Applications > Helm.

  4. On the Helm page, find the ack-onepilot application and click Delete in the Actions column.

  5. In the Delete dialog box, click OK.

    This action uninstalls the ack-onepilot component for MSE Microservices Governance.

Important

  • The ack-onepilot component is required for MSE and ARMS Java agent access. After you delete the ack-onepilot component, pods in the current cluster can no longer automatically connect to MSE or ARMS.

  • Restart any application pods already connected to MSE to finalize the disconnection from Microservices Governance.

Remove a microservice application in MSE

Note

Before you remove an application, consider the following:

  • Check node connections: On the application's Node details page, verify that all nodes are disconnected before you remove the application or disable MSE.

  • Redeploy after removal or disabling: After confirming that all nodes are disconnected, remove the application or disable MSE. If you have deleted the ack-onepilot component or disabled MSE using labels, you must redeploy the applications to ensure they run correctly.

  1. Log on to the MSE console, and select a region in the top navigation bar.

  2. In the left-side navigation pane, choose Microservices Governance > Application Governance.

  3. On the Applications page, hover over the target application's card. When the Remove button appears in the upper-right corner, click Remove.

    To remove multiple applications, click Batch Select at the bottom of the page, select the applications you want to remove or select all, and then click Batch Delete.

  4. In the Remove confirmation dialog box, click OK.

Related documentation

For information about billing for Microservices Governance, see Billing overview of Microservices Governance.

Previous：Install and update the MSE Microservices Governance componentNext：Cloud-native gateways