Help Center/ Application Operations Management/ User Guide (2.0) (Kuala Lumpur Region)/ FAQs/ Container Insights/ Why Can't AOM Detect Workloads After the Pod YAML File Is Deployed Using Helm?
Updated on 2024-08-05 GMT+08:00
View PDF
Share

Why Can't AOM Detect Workloads After the Pod YAML File Is Deployed Using Helm?

Symptom

After the pod YAML file is deployed using Helm, AOM cannot detect workloads.

Possible Cause

Compare the YAML file deployed using Helm with that deployed on the CCE console. Environment parameters are found missing in the file deployed using Helm.

Figure 1 Comparing YAML files

Solution

  1. Log in to the CCE console and click a target cluster.
  2. Choose Workloads in the navigation pane, and select the type of workload whose metrics are to be reported to AOM.
  3. Choose More > Edit YAML in the Operation column where the target workload is located.
  4. In the displayed dialog box, locate spec.template.spec.containers.
  5. Add environment parameters to the end of the image field, as shown in Figure 2.

    Figure 2 Adding environment parameters

  6. Click Confirm.
Parent topic: Container Insights