You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/aks/aks-diagnostics.md
+5-8Lines changed: 5 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,11 +7,11 @@ ms.date: 11/15/2022
7
7
8
8
# Azure Kubernetes Service Diagnostics (preview) overview
9
9
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 that:
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:
11
11
12
12
* Helps you identify and resolve problems in your cluster.
13
13
* Is cloud-native.
14
-
* Requires no extra configuration or billing cost.
14
+
* Requires no extra configuration or billing costs.
15
15
16
16
[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
17
17
@@ -22,22 +22,19 @@ To access AKS Diagnostics:
22
22
1. Sign in to the [Azure portal](https://portal.azure.com)
23
23
1. From **All services** in the Azure portal, select **Kubernetes Service**.
24
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_, by:
26
-
27
-
* Using the keywords in the homepage tile.
28
-
* Typing a keyword that best describes your issue in the search bar.
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.
After you click on 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:
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:
35
32
36
33
* Issues
37
34
* Recommended actions
38
35
* Links to helpful docs
39
36
* Related-metrics
40
-
* Logging data
37
+
* Logging data
41
38
42
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.
Copy file name to clipboardExpand all lines: articles/aks/auto-upgrade-cluster.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ If using the `node-image` cluster auto-upgrade channel or the `NodeImage` node i
38
38
39
39
## Using cluster auto-upgrade
40
40
41
-
Automatically completed upgrades are functionally the same as manual upgrades. The timing of upgrades is determined by the selected channel. When making changes to auto-upgrade, allow 24 hours for the changes to take effect.
41
+
Automatically completed upgrades are functionally the same as manual upgrades. The timing of upgrades is determined by the [selected auto-upgrade channel][planned-maintenance]. When making changes to auto-upgrade, allow 24 hours for the changes to take effect.
Copy file name to clipboardExpand all lines: articles/aks/manage-abort-operations.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,13 +28,12 @@ The abort operation supports the following scenarios:
28
28
29
29
You can use the [az aks nodepool](/cli/azure/aks/nodepool) command with the `operation-abort` argument to abort an operation on a node pool or a managed cluster.
30
30
31
-
The following example terminates an operation on a node pool on a specified cluster by its name and resource group that holds the cluster.
32
-
31
+
The following example terminates an operation on a node pool on a specified cluster.
33
32
```azurecli-interactive
34
33
az aks nodepool operation-abort --resource-group myResourceGroup --cluster-name myAKSCluster --name myNodePool
35
34
```
36
35
37
-
The following example terminates an operation against a specified managed cluster its name and resource group that holds the cluster.
36
+
The following example terminates an operation on a specified cluster.
38
37
39
38
```azurecli-interactive
40
39
az aks operation-abort --name myAKSCluster --resource-group myResourceGroup
@@ -52,7 +51,7 @@ The following example terminates a process for a specified agent pool.
0 commit comments