How to disable MSE microservice governance - Microservices Engine

If you no longer use the MSE Microservice Governance Center, promptly disable MSE microservice governance to avoid affecting your applications. This topic describes how to disable MSE microservice governance.

Disable MSE microservice governance for a Kubernetes namespace

Log on to the MSE Governance Center.
In the navigation pane on the left, choose O&M Center. At the top of the page, select Kubernetes Clusters, and then click the name of the target cluster.
In the Actions column of the target namespace, click Deactivate Microservice Governance.

Note

Disabling MSE microservice governance for a Kubernetes namespace does not affect applications that are connected using the single-application connection type. To disable governance for these applications, see the procedure for a single application later in this topic.
After you disable MSE microservice governance for a Kubernetes namespace, you can still connect applications in the namespace to MSE microservice governance using the single-application connection type.
Applications in the Kubernetes namespace that are already connected to MSE must be restarted to disable microservice governance.

Disable MSE microservice governance for a single Java application

Log on to the ACK console.
In the left-side navigation pane, click Clusters. Then, click the name of the cluster that you want to manage.
In the left-side navigation pane, choose Workloads > Deployments.
In the upper-left corner of the Deployments page, select a Namespace. In the Actions column of the target application, choose More > Edit YAML.
In the Edit YAML dialog box, navigate to spec > Template > Metadata and find `labels`. Delete msePilotAutoEnable: "on" or change it to msePilotAutoEnable: "off", and then click Update.
```
labels:
  msePilotAutoEnable: "off"
```

Uninstall the MSE Governance Center component in ACK

Log on to the ACK console.
In the left-side navigation pane, click Clusters. Then, click the name of the cluster that you want to manage.
In the left-side navigation pane, choose Applications > Helm.
On the Helm page, find the ack-onepilot application and click Delete in the Actions column.
In the Delete dialog box, click OK.
The MSE Governance Center component ack-onepilot is uninstalled.

Important

The ack-onepilot component is used to connect MSE and ARMS Java agents. After you delete the ack-onepilot component, pods in the cluster cannot be automatically connected to MSE or ARMS.
Application pods already connected to MSE must be restarted to disable microservice governance.

Delete a microservice application in MSE

Note

Before you delete an application, note the following:

Check node connections: On the Node Details page of the application, verify which nodes are connected. Ensure that all nodes have disconnected from the application before you delete or disable MSE.
Redeploy after deleting or disabling MSE: After you confirm that all nodes have disconnected, you can delete or disable MSE. If you delete ack-onepilot or disable MSE using labels, you must redeploy the application to ensure that it continues to run properly.

Log on to the MSE console, and select a region in the top navigation bar.
In the left-side navigation pane, choose Microservices Governance > Application Governance.
On the Application List page, hover the mouse pointer over the target application card. 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 that you want to remove, and then click Batch Remove.
In the Remove confirmation dialog box, click OK.

References

For more information about billing for microservice governance, see Billing overview of microservice governance.