|
1 | 1 | --- |
2 | | -title: Azure Kubernetes Service (AKS) Diagnostics Overview |
| 2 | +title: Azure Kubernetes Service (AKS) Diagnose and Solve Problems Overview |
3 | 3 | description: Learn about self-diagnosing clusters in Azure Kubernetes Service. |
| 4 | +services: container-service |
| 5 | +author: rongzhang |
4 | 6 | ms.topic: conceptual |
5 | | -ms.date: 11/15/2022 |
| 7 | +ms.date: 03/10/2023 |
| 8 | +ms.author: rongzhang |
6 | 9 | --- |
7 | 10 |
|
8 | | -# Azure Kubernetes Service Diagnostics (preview) overview |
| 11 | +# Azure Kubernetes Service Diagnose and Solve Problems overview |
9 | 12 |
|
10 | | -Troubleshooting Azure Kubernetes Service (AKS) cluster issues plays an important role in maintaining your cluster, especially if your cluster is running mission-critical workloads. AKS Diagnostics (preview) is an intelligent, self-diagnostic experience with the following features: |
| 13 | +Troubleshooting Azure Kubernetes Service (AKS) cluster issues plays an important role in maintaining your cluster, especially if your cluster is running mission-critical workloads. AKS Diagnose and Solve Problems is an intelligent, self-diagnostic experience that: |
| 14 | +* Helps you identify and resolve problems in your cluster. |
| 15 | +* Requires no extra configuration or billing cost. |
| 16 | + |
| 17 | +## Open AKS Diagnose and Solve Problems |
11 | 18 |
|
12 | | -* Helps you identify and resolve problems in your cluster. |
13 | | -* Is cloud-native. |
14 | | -* Requires no extra configuration or billing costs. |
| 19 | +To access AKS Diagnose and Solve Problems: |
15 | 20 |
|
16 | | -[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)] |
| 21 | +1. Navigate to your Kubernetes cluster in the [Azure portal](https://portal.azure.com). |
| 22 | +2. Click on **Diagnose and solve problems** in the left navigation, which opens AKS Diagnose and Solve Problems. |
| 23 | +3. Choose a category that best describes the issue of your cluster by: |
| 24 | + * Referring the keywords in each tile description on the homepage. |
| 25 | + * Typing a keyword that best describes your issue in the search bar. |
17 | 26 |
|
18 | | -## Open AKS Diagnostics |
| 27 | + |
19 | 28 |
|
20 | | -To access AKS Diagnostics: |
21 | | - |
22 | | -1. Sign in to the [Azure portal](https://portal.azure.com) |
23 | | -1. From **All services** in the Azure portal, select **Kubernetes Service**. |
24 | | -1. Select **Diagnose and solve problems** in the left navigation, which opens AKS Diagnostics. |
25 | | -1. Choose a category that best describes the issue of your cluster, like _Cluster Node Issues_, using the keywords in the homepage tile or typing a keyword that best describes your issue in the search bar. |
26 | | - |
27 | | - |
28 | 29 |
|
29 | 30 | ## View a diagnostic report |
30 | 31 |
|
31 | | -After selecting a category, you can view a diagnostic report specific to your cluster. Diagnostic reports intelligently call out any issues in your cluster with status icons. You can drill down on each topic by clicking **More Info** to see a detailed description of: |
| 32 | +To initiate the tool and retrieve the results in a seamless manner, click on the tile to troubleshoot. The left navigation pane has an _Overview_ option which runs all the diagnostics in that particular category. The issues that are found with the cluster will be displayed on the right panel. To obtain a comprehensive understanding of the issue, click on View details for each tile, which will provide a detailed description of: |
32 | 33 |
|
33 | | -* Issues |
| 34 | +* Issue summary |
| 35 | +* Error details |
34 | 36 | * Recommended actions |
35 | 37 | * Links to helpful docs |
36 | 38 | * Related-metrics |
37 | 39 | * Logging data |
38 | 40 |
|
39 | | -Diagnostic reports generate based on the current state of your cluster after running various checks. They can be useful for pinpointing the problem of your cluster and understanding next steps to resolve the issue. |
| 41 | +Based on the outcome, you may follow the detailed instructions or peruse the documentation links to effectively resolve the issue at hand. |
40 | 42 |
|
41 | | - |
| 43 | +**Example scenario 1**: I observed that my application is getting disconnected or experiencing intermittent connection issues. In response, I click **Connectivity Issues** tile to investigate the potential causes. |
42 | 44 |
|
43 | | - |
| 45 | + |
44 | 46 |
|
45 | | -## Cluster insights |
| 47 | +I received a diagnostic alert indicating that the disconnection may be related to my *Cluster DNS*. To gather more information, I clicked on *View details*. |
46 | 48 |
|
47 | | -The following diagnostic checks are available in **Cluster Insights**. |
| 49 | + |
48 | 50 |
|
49 | | -### Cluster Node Issues |
| 51 | +Based on the diagnostic result, it appears that the issue may be related to known DNS issues or VNET configuration. Thankfully, I can use the documentation links provided to address the issue and resolve the problem. |
50 | 52 |
|
51 | | -Cluster Node Issues checks for node-related issues that cause your cluster to behave unexpectedly. Specifically: |
| 53 | + |
52 | 54 |
|
53 | | -- Node readiness issues |
54 | | -- Node failures |
55 | | -- Insufficient resources |
56 | | -- Node missing IP configuration |
57 | | -- Node CNI failures |
58 | | -- Node not found |
59 | | -- Node power off |
60 | | -- Node authentication failure |
61 | | -- Node kube-proxy stale |
| 55 | +Furthermore, if the recommended documentation based on the diagnostic results does not resolve the issue, you can return to the previous step in Diagnostics and refer to additional documentation. |
62 | 56 |
|
63 | | -### Create, read, update & delete (CRUD) operations |
| 57 | + |
64 | 58 |
|
65 | | -CRUD Operations checks for any CRUD operations that cause issues in your cluster. Specifically: |
| 59 | +## Use AKS Diagnose and Solve Problems for Best Practices |
66 | 60 |
|
67 | | -- In-use subnet delete operation error |
68 | | -- Network security group delete operation error |
69 | | -- In-use route table delete operation error |
70 | | -- Referenced resource provisioning error |
71 | | -- Public IP address delete operation error |
72 | | -- Deployment failure due to deployment quota |
73 | | -- Operation error due to organization policy |
74 | | -- Missing subscription registration |
75 | | -- VM extension provisioning error |
76 | | -- Subnet capacity |
77 | | -- Quota exceeded error |
| 61 | +Deploying applications on AKS requires adherence to best practices to guarantee optimal performance, availability, and security. To this end, the AKS Diagnose and Solve Problems **Best Practices** tile provides an array of best practices that can assist in managing various aspects such as VM resource provisioning, cluster upgrades, scaling operations, subnet configuration, and other essential aspects of a cluster's configuration. Leveraging the AKS Diagnose and Solve Problems can be vital in ensuring that your cluster adheres to best practices and that any potential issues are identified and resolved in a timely and effective manner. By incorporating AKS Diagnose and Solve Problems into your operational practices, you can be confident in the reliability and security of your application in production. |
78 | 62 |
|
79 | | -### Identity and security management |
| 63 | +**Example Scenario 2**: My cluster seems to be in good health. All nodes are ready, and my application runs without any issues. However, I am curious about the best practices I can follow to prevent potential problems. So, I click on the **Best Practices** tile. After reviewing the recommendations, I discovered that even though my cluster appears healthy at the moment, there are still some things I can do to avoid latency, throttling or VM uptime issues in the future. |
80 | 64 |
|
81 | | -Identity and Security Management detects authentication and authorization errors that prevent communication to your cluster. Specifically, |
| 65 | + |
82 | 66 |
|
83 | | -- Node authorization failures |
84 | | -- 401 errors |
85 | | -- 403 errors |
| 67 | + |
86 | 68 |
|
87 | 69 | ## Next steps |
88 | 70 |
|
|
0 commit comments