If you no longer use the Microservices Engine (MSE) Microservice Governance Center, disable MSE microservice governance promptly to avoid affecting your applications. Applications that are already connected to MSE must be restarted after governance is disabled.
MSE provides four methods to disable or remove governance, each targeting a different scope. Pick the method that matches what you originally enabled.
Choose a method
| Method | Scope | Mechanism | When to use |
|---|---|---|---|
| Deactivate governance for a namespace | All applications in a Kubernetes namespace | MSE console | Stop governance for an entire namespace at once |
| Disable governance for a single application | One Java application | Deployment label (msePilotAutoEnable) | Stop governance for one application without affecting the namespace |
| Uninstall the ack-onepilot component | Entire ACK cluster | Helm release deletion | Fully remove the MSE agent injection mechanism from a cluster |
| Delete an application from MSE | MSE console records | Console cleanup | Remove application entries from the MSE console after governance is disabled |
Namespace-level deactivation and single-application disabling are independent. Deactivating governance for a namespace does not affect applications connected through the single-application connection type, and vice versa.
Prerequisites
Before you begin, ensure that you have:
A maintenance window scheduled for pod restarts -- applications already connected to MSE require a restart after governance is disabled
An understanding of the billing impact -- see Billing overview of microservice governance
Deactivate governance for a Kubernetes namespace
Deactivate governance at the namespace level to stop MSE governance for all applications in a Kubernetes namespace at once.
Log on to the MSE Governance Center.
In the left-side navigation pane, 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.
Restart all application pods in the namespace that were previously connected to MSE. Governance remains active on running pods until they restart.
What happens after deactivation:
| Item | Status |
|---|---|
| Namespace-level governance | Disabled for new and restarted pods |
| Running pods (not restarted) | Governance remains active until pod restart |
| Single-application connections | Not affected -- still active if previously enabled |
After namespace-level governance is deactivated, you can still connect individual applications in that namespace through the single-application connection type. To disable governance for those applications, see Disable governance for a single Java application.
Disable governance for a single Java application
Modify the deployment labels in the application's YAML configuration to disable governance for a specific Java application without affecting the rest of the namespace.
Log on to the Container Service for Kubernetes (ACK) console.
In the left-side navigation pane, click Clusters. Click the name of the cluster that contains your application.
In the left-side navigation pane, choose Workloads > Deployments.
In the upper-left corner of the Deployments page, select the target Namespace. In the Actions column of the target application, choose .
In the Edit YAML dialog box, navigate to spec > Template > Metadata >
labels. Delete themsePilotAutoEnable: "on"label or change its value to"off":labels: msePilotAutoEnable: "off"Click Update.
What happens after disabling:
| Item | Status |
|---|---|
| Target application governance | Disabled after pod restart |
| Other applications in the namespace | Not affected |
| Namespace-level governance | Not affected |
The msePilotAutoEnable label | Remains in the YAML with value "off" |
Uninstall the ack-onepilot component
The ack-onepilot component automatically injects MSE and Application Real-Time Monitoring Service (ARMS) Java agents into application pods. Uninstalling it stops all automatic agent injection across the cluster.
After you uninstall ack-onepilot, pods in the cluster can no longer connect to MSE or ARMS automatically. Pods that are already connected must be restarted to fully disable governance.
Log on to the ACK console.
In the left-side navigation pane, click Clusters. 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.
What happens after uninstalling:
| Item | Status |
|---|---|
ack-onepilot Helm release | Removed from the cluster |
| New pods | No longer injected with MSE or ARMS agents |
| Running pods (already connected) | Governance remains active until pod restart |
| MSE console application entries | Remain until you manually delete them |
Delete a microservice application from MSE
After governance is disabled, remove the application entries from the MSE console to keep your workspace clean.
Before you delete an application, go to its Node Details page and confirm that all nodes have disconnected. If you previously deleted ack-onepilot or disabled governance through labels, redeploy the application first to make sure it runs properly without the governance layer.
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 over the target application card. Click Remove in the upper-right corner of the card.
To remove multiple applications at once, click Batch Select at the bottom of the page, select the applications, and then click Batch Remove.
In the Remove confirmation dialog box, click OK.