Scan ACK clusters for potential risks such as resource quota shortages, and apply suggested fixes.
Usage notes
-
Inspection results are retained for 7 days.
-
During inspection, ACK collects key error messages from system logs and operation data such as system version, loads, Docker, and kubelet. It does not collect business data or sensitive information.
Prerequisites
Before you begin, ensure that you have:
-
An ACK cluster is in Running state. Verify on the Clusters page of the ACK console.
Set up a scheduled inspection
-
Log on to the ACK console. In the left-side navigation pane, click Clusters.
-
On the Clusters page, click the target cluster name. In the left-side navigation pane, choose Inspections and Diagnostics > Cluster Inspections.
-
In the Schedule Rule section of the Cluster Inspection page, click Add.
-
In the Set Inspection Rule pane, set TimeZone and Regular Task Rule (Daily), confirm the cluster information, and save. ACK inspects the cluster daily at the scheduled time. To run an inspection immediately, click Start in the Reports section. Results appear in the Reports section after the inspection completes.
View inspection results
In the Reports section of the Cluster Inspection page, click Details in the Operation column of the report.
The report lists risks by severity: Warning, Error, and Critical. Critical risks are highlighted. Each risk shows its severity, impact, and recommended solution. Follow the console guidance to resolve issues.
Subscribe to inspection reports
In the Subscribe Reports section of the Cluster Inspection page, log on to the Advisor Console to configure report subscriptions.
Manage inspection rules
In the Schedule Rule section of the Cluster Inspection page:
-
Click Edit to modify a rule.
-
Click Delete to remove a rule. The cluster is no longer inspected on that schedule.
Next steps
-
Cluster check: verify that your cluster meets requirements before operations such as upgrades or migrations.
-
Cluster diagnostics: diagnose nodes, pods, Services, and Ingresses to locate cluster issues.