Alibaba Cloud Container Service for Kubernetes (ACK) provides a one-click diagnostics feature through the Container Intelligent Service. This feature includes Pod diagnostics, Service diagnostics, and Ingress diagnostics to help you pinpoint issues in your cluster. This topic describes how to use cluster diagnostics in an ACK cluster.
Diagnostic features
Container Intelligent Service provides the following diagnostic features:
|
Diagnostic item |
Description |
|
Diagnoses issues with Pods, such as startup failures and frequent restarts. |
|
|
Diagnoses issues with Services, such as misconfigurations, resource quotas, and abnormal events. |
|
|
Diagnoses issues with Ingress resources, such as traffic configuration problems. |
Run a diagnosis
The diagnostics feature runs a data collection program on your cluster to collect inspection results. The collected information includes the system version, load, the running status of container components, and key error messages from system logs. The data collection program does not collect your business data or sensitive data.
The procedures for running diagnostics on Pods, Services, and Ingresses are similar. The following steps use Pod diagnostics as an example.
-
Log on to the ACK console. In the left-side navigation pane, select Clusters.
-
On the Clusters page, click the target cluster. In the left-side navigation pane, choose . If prompted, complete the authorization.
-
On the Diagnostics page, click Pod diagnostics.
-
On the Pod diagnostics page, click Diagnose.
-
In the Select Pod panel, select a Namespace and a Pod. Read the notice, select I know and agree, and then click Create diagnosis.
NoteYou can track the diagnostic progress on the page. After the diagnosis is complete, the page displays the results and a list of diagnostic items. Use this information to identify and fix any issues.
View diagnostic results
On the Diagnostics page, find the report and click Diagnosis details in the Actions column.
The specific diagnostic items may vary depending on your cluster configuration. For actual results, refer to the diagnostics page.
|
Diagnostic item |
Status |
Description |
|
Pod diagnostics |
|
Pod diagnostics includes the Pod and ClusterComponent diagnostic items. It determines the cause of Pod anomalies by checking the Pod status and the health of cluster components. On the details page, you can view the diagnostic results, recommended solutions, and a list of specific diagnostic items. Hover over the information icon Items with an Abnormal or Warning status appear on the Pending tab. For items with an Abnormal status, hover over View Details in the Status column to view the error details. |
|
Service diagnostics |
Service diagnostics includes the Service and resource quotas diagnostic items. It determines the cause of Service anomalies by checking items such as the billing type of the Classic Load Balancer (CLB) instance, certificates, resource quotas, and abnormal events. Hover over the information icon Items with an Abnormal or Warning status appear on the Pending tab. For items with an Abnormal status, hover over View Details in the Status column to view the error details. |
|
|
Ingress diagnostics |
Ingress diagnostics includes the Ingress, Addon, and Server Load Balancer (SLB) diagnostic items. It determines the cause of Ingress anomalies by checking the Ingress status, the health of Ingress add-ons, and the status of the SLB instance. Hover over the information icon Items with an Abnormal or Warning status appear on the Pending tab. For items with an Abnormal status, hover over View Details in the Status column to view the error details. |
: No action is required.
: Review and address issues that may cause cluster anomalies.
: Take action immediately to prevent the cluster from malfunctioning.
: The check did not complete or the result is unavailable.
to the right of a diagnostic item to view its description.