All Products
Search
Document Center

Application Real-Time Monitoring Service:Why does an ARMS agent fail to install in an ACK cluster?

Last Updated:Mar 11, 2026

If the Application Real-Time Monitoring Service (ARMS) agent fails to install for an application in a Container Service for Kubernetes (ACK) cluster, the cause is that the ARMS Addon Token does not exist in the cluster that you want to manage.

To resolve this, verify that the token exists and then grant the required permissions.

Step 1: Check whether the ARMS Addon Token exists

  1. Log on to the ACK console. In the left-side navigation pane, click Clusters, and then click the name of your cluster.

  2. In the left-side navigation pane, choose Configurations > Secrets.

  3. Select kube-system from the Namespace drop-down list and check whether addon.arms.token exists.

    ARMS Addon Token

Step 2: Grant ACK permissions to access ARMS

If the token is missing, grant the cluster worker nodes access to ARMS by manually adding the required Resource Access Management (RAM) permission policies.

  1. Log on to the ACK console. In the left-side navigation pane, click Clusters, and then click the name of your cluster.

  2. On the Basic Information tab of the Cluster Information page, find the Cluster Resources section and click the link next to Worker RAM Role.

  3. On the RAM page that appears, click Grant Permission on the Permissions tab.

  4. In the Grant Permission panel, add the following policies and click Grant permissions:

    PolicyDescription
    AliyunTracingAnalysisFullAccessFull access to Managed Service for OpenTelemetry
    AliyunARMSFullAccessFull access to ARMS