Application Real-Time Monitoring Service:Why does an ARMS agent fail to be installed for an application in an ACK cluster?

Possible cause

ARMS Addon Token does not exist in the cluster that you want to manage.

Solutions

Step 1: Check whether ARMS Addon Token exists in the cluster

1. Log on to the ACK console. In the left-side navigation pane, click Clusters. On the Clusters page, click the name of the cluster to go to the cluster details page.

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

3. In the upper part of the page, select kube-system from the Namespace drop-down list and check whether addon.arms.token is displayed on the Secrets page.

Step 2: Grant ACK the permissions to access ARMS

1. Log on to the ACK console.
2. In the left-side navigation pane, click Clusters. On the Clusters page, click the cluster name or click Details in the Actions column.
3. On the Cluster Information page of the cluster, click the Cluster Resources tab. On the Cluster Resources tab, click the hyperlink next to Worker RAM Role.
4. You are redirected to the Roles page in the RAM console. On the Roles page, click the policy name on the Permissions tab.
5. On the Policy Document tab, click Modify Policy Document, add the following code in the code editor, and then click Next to edit policy information.

   {
      "Action": "arms:*",
      "Resource": "*",
      "Effect": "Allow"
   }

   
6. Click OK.