Uninstall arms-pilot and install ack-onepilot

The legacy application monitoring component arms-pilot is no longer maintained. You can install the upgraded ack-onepilot component to monitor your applications. ack-onepilot is fully compatible with arms-pilot, allowing a seamless migration without changing your application configurations. This topic describes how to uninstall arms-pilot and install ack-onepilot.

Before you begin

The ack-onepilot component cannot be installed on an ACK cluster that runs a Kubernetes version earlier than 1.16. If your cluster version is earlier than 1.16, upgrade your cluster first. For more information, see Upgrade the Kubernetes version of an ACK cluster.
You must uninstall arms-pilot before you install ack-onepilot. If both components are installed at the same time, the agent fails to mount.
Custom configurations for arms-pilot are not automatically migrated to ack-onepilot. Before you start, save your existing configurations and then apply them to ack-onepilot after you install it.
Wait until arms-pilot is completely uninstalled before you install ack-onepilot. Otherwise, ack-onepilot may detect remaining arms-pilot resources and fail to start.

Uninstall arms-pilot

Log on to the ACK console. On the Clusters page, click the name of the cluster.
In the left-side navigation pane, choose Applications > Helm.
On the Helm page, find arms-pilot and click Delete in the Actions column.
In the Delete confirmation dialog box, click OK.

Verify the uninstallation

In the ACK console, go to the Workloads > Deployments page for the target cluster. At the top of the page, set the namespace to arms-pilot and confirm that the pods in this namespace are deleted.

Note

If you installed the arms-pilot component in a custom namespace, select that namespace instead.

Install ack-onepilot

Log on to the ACK console. On the Clusters page, click the name of the cluster.
In the left-side navigation pane, click Add-ons. On the Add-ons page, search for ack-onepilot.
Click Install on the ack-onepilot card.

Note
By default, the ack-onepilot component supports 1,000 pods. For every additional 1,000 pods in the cluster, you must add 0.5 CPU cores and 512 MB memory for the component.
In the dialog box that appears, configure the parameters and click OK. We recommend that you use the default values.

Note
After you install ack-onepilot, you can upgrade, configure, or uninstall it on the Add-ons page.

Verify the installation

Go to the Workloads > Deployments page for the target cluster in the ACK console. At the top of the page, select ack-onepilot for Namespace and confirm that the pods in the namespace are running.

Verify that the Number of Pods column shows 2/2, which indicates that all pod replicas are ready.