The arms-pilot Application Monitoring agent is no longer maintained. Its replacement, ack-onepilot, is fully compatible and requires no changes to your application configurations. This guide covers uninstalling arms-pilot and installing ack-onepilot on an ACK cluster.
You must uninstall arms-pilot before you install ack-onepilot. If both agents are present in the cluster, the ARMS agent cannot mount. If any arms-pilot resources remain, ack-onepilot detects them and does not start.
Prerequisites
Before you begin, make sure that you have:
An ACK cluster running Kubernetes V1.16 or later. If your cluster runs an earlier version, update the Kubernetes version first
A record of your current
arms-pilotconfigurations. These are not automatically carried over toack-onepilotand must be manually re-applied after installation
Uninstall arms-pilot
Log on to the ACK console. On the Clusters page, click the name of your 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 dialog box, click OK.
Verify the uninstallation
In the left-side navigation pane, choose Workloads > Deployments.
On the Deployments page, select arms-pilot from the Namespace drop-down list.
NoteIf you previously changed the namespace for
arms-pilot, select that namespace instead.Confirm that all pods in the namespace have been deleted.
Do not proceed to the next step until all arms-pilot resources are removed. Remaining resources prevent ack-onepilot from starting.
Install ack-onepilot
Log on to the ACK console. On the Clusters page, click the name of your cluster.
In the left-side navigation pane, click Add-ons.
On the Add-ons page, search for ack-onepilot and click Install on its card.
In the dialog box, configure the parameters and click OK. The default values work for most clusters.
ack-onepilotresource requirements scale with the number of pods in the cluster:Pods in cluster CPU (cores) Memory Up to 1,000 Default Default Each additional 1,000 +0.5 +512 MB Re-apply any
arms-pilotconfigurations that you recorded in the prerequisites step.
After installation, you can upgrade, configure, or uninstall ack-onepilot from the Add-ons page.
Verify the installation
In the left-side navigation pane, choose Workloads > Deployments.
On the Deployments page, select ack-onepilot from the Namespace drop-down list.
Confirm that all pods in the namespace are running.
