All Products
Search
Document Center

Container Service for Kubernetes:Work with the cluster inspection feature

Last Updated:Apr 11, 2025

Container Intelligence Service (CIS) provides the cluster inspection feature. It scans cluster health to detect potential risks and provides corresponding solutions. Checks include remaining cloud resource quotas and key resource levels in Container Service for Kubernetes (ACK) clusters.

Procedure

Before proceeding with the cluster inspection feature, ensure the cluster is in a normal running state.

On the Clusters page of the ACK console, confirm that the target cluster's status is Running.
Important

When you use the cluster inspection feature, ACK runs a data collection program in the cluster to collect inspection results. The program collects key error messages from the system log and operation information, such as the system version, loads, Docker, and kubelet. The data collection program does not collect business information or sensitive data.

  1. Log on to the ACK console. In the left-side navigation pane, click Clusters.

  2. On the Clusters page, find the cluster that you want to manage and click its name. In the left-side pane, choose Inspections and Diagnostics > Cluster Inspections.

  3. In the Schedule Rule section of the Cluster Inspection page, click Add.

  4. In the Set Inspection Rule pane, specify TimeZone and Regular Task Rule (Daily), confirm cluster information, read the warning message, and save the configuration as prompted.

    After you configure the cluster inspection feature, ACK inspects the cluster at the scheduled time.

    In the Reports section of the Cluster Inspection page, you can click Start to manually trigger a cluster inspection. After the inspection is complete, the results are displayed in the Reports section.

  5. After the inspection is finished, in the Reports section of the Cluster Inspection page, click Details in the Operation column of the report you want to view.

    • Risks are displayed in ascending order of severity levels, including Warning, Error, and Critical. Critical-level risks are highlighted.

    • A inspection report includes the identified risks and their severity levels, impacts, and solutions. Refer to the guide in the console to diagnose and resolve them.

What to do next

Subscribe to cluster inspection reports

The cluster inspection feature allows you to subscribe to cluster inspection reports. In the Subscribe Reports section of the Cluster Inspection page, log on to the Advisor Console to configure inspection report subscription.

Manage the inspection rule

After you configure cluster inspection, you can perform the following operations in the Schedule Rule section:

  • Click Edit to modify the inspection rule.

  • Click Delete to delete inspection rules that you no longer use. After an inspection rule is deleted, the cluster is no longer inspected based on the rule.

References

  • Cluster check can be used to check whether your ACK cluster meets the requirements before operations such as upgrade or migration.

  • Cluster diagnostics provides troubleshooting for nodes, pods, Services, Ingress, memory, and networks to identify issues.