When pods fail to start, Services become unreachable, or Ingress routing breaks down, cluster diagnostics lets you pinpoint the root cause with a single click. Container Intelligent Service runs automated checks across pods, Services, and Ingresses in your Alibaba Cloud Container Compute Service (ACS) cluster, returning flagged issues with repair suggestions so you can act immediately.
Diagnostic items
Three diagnostic types are available:
| Diagnostic item | What it checks |
|---|---|
| Pod diagnostics | Pod status issues, such as startup failures and frequent restarts |
| Service diagnostics | Service configurations, resource quotas, and abnormal events |
| Ingress diagnostics | Traffic routing configurations |
How it works
Important
When you start a diagnosis, the system runs a data collection program on each node in the cluster. The program collects the system version, loads, container component status, and key error messages from system logs. It does not collect business data or sensitive information.
Prerequisites
Before you begin, ensure that you have:
-
An ACS cluster
-
Access to the ACS console
-
Authorization for Inspections and Diagnostics > Diagnostics (you will be prompted to complete authorization on first access)
Run a diagnosis
The steps for Pod, Service, and Ingress diagnostics follow the same pattern. The following example uses Pod diagnostics.
-
Log in to the ACS console. In the left-side navigation pane, click Clusters.
-
On the Clusters page, click the name of the cluster you want to manage. In the left-side navigation pane, choose Inspections and Diagnostics > Diagnostics and complete the authorization steps.
-
On the Diagnosis page, click Pod diagnosis.
-
On the Pod diagnosis page, click Diagnosis.
-
In the Select Pod panel, select a Namespace and a Pod, read and accept the warning by selecting I know and agree, and then click Create diagnosis.
Diagnostic progress appears on the page. After the diagnosis completes, the results and flagged items appear. Review each flagged item to identify the cause and resolve the issue.
View diagnostic results
On the Pod diagnosis page, click Diagnosis details in the Operation column to open the details page for a diagnostic report.
Diagnostic items vary based on cluster configuration. The items shown on the diagnostic page reflect your cluster's actual configuration.
The details page shows the following information for each diagnostic item:
-
Issue summary and diagnostic status
-
Repair suggestions
-
Related diagnostic items
Diagnostic flags
Each diagnostic item displays one of the following flags:
| Flag | Meaning | Recommended action |
|---|---|---|
| Normal | No issues detected | No action required |
| Warning | A potential issue exists that may affect cluster stability | Review the item and resolve issues that could cause cluster anomalies |
| Abnormal | An active issue is affecting the cluster | Troubleshoot immediately to prevent cluster errors |
| Unknown | The diagnosis did not complete or the result is unavailable | — |
To view details for an item with the Abnormal flag, hover over Details in the Status column. To view a description of any diagnostic item, hover over the information icon to the right of the item.
Items flagged as Abnormal or Warning are listed on the Troubleshoot tab for quick access.
Diagnostic item reference
Pod diagnostics
Pod diagnostics include the Pod and ClusterComponent diagnostic items. The check covers pod status anomalies and cluster component health. The details page shows pod diagnostic results, repair suggestions, and related diagnostic items.
Service diagnostics
Service diagnostics include the Service and ResourceQuotas diagnostic items. The check covers the billing method of Classic Load Balancer (CLB) instances, certificates, resource quotas, and abnormal events.
Ingress diagnostics
Ingress diagnostics include the Ingress, Addon, and SLB diagnostic items. The check covers Ingress status, Ingress plug-in health, and Server Load Balancer (SLB) instance status.