Skip to content

Commit 90a4689

Browse files
Merge pull request #235621 from schaffererin/aks-mvp-feedback
Incorporating relevant feedback from MVP summit
2 parents 5e14369 + 0d9d866 commit 90a4689

File tree

3 files changed

+9
-13
lines changed

3 files changed

+9
-13
lines changed

articles/aks/aks-diagnostics.md

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,11 +7,11 @@ ms.date: 11/15/2022
77

88
# Azure Kubernetes Service Diagnostics (preview) overview
99

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:
1111

1212
* Helps you identify and resolve problems in your cluster.
1313
* Is cloud-native.
14-
* Requires no extra configuration or billing cost.
14+
* Requires no extra configuration or billing costs.
1515

1616
[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
1717

@@ -22,22 +22,19 @@ To access AKS Diagnostics:
2222
1. Sign in to the [Azure portal](https://portal.azure.com)
2323
1. From **All services** in the Azure portal, select **Kubernetes Service**.
2424
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.
2926

3027
![Homepage](./media/concepts-diagnostics/aks-diagnostics-homepage.png)
3128

3229
## View a diagnostic report
3330

34-
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:
3532

3633
* Issues
3734
* Recommended actions
3835
* Links to helpful docs
3936
* Related-metrics
40-
* Logging data
37+
* Logging data
4138

4239
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.
4340

articles/aks/auto-upgrade-cluster.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ If using the `node-image` cluster auto-upgrade channel or the `NodeImage` node i
3838

3939
## Using cluster auto-upgrade
4040

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.
4242

4343
The following upgrade channels are available:
4444

articles/aks/manage-abort-operations.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -28,13 +28,12 @@ The abort operation supports the following scenarios:
2828

2929
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.
3030

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.
3332
```azurecli-interactive
3433
az aks nodepool operation-abort --resource-group myResourceGroup --cluster-name myAKSCluster --name myNodePool
3534
```
3635

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.
3837

3938
```azurecli-interactive
4039
az aks operation-abort --name myAKSCluster --resource-group myResourceGroup
@@ -52,7 +51,7 @@ The following example terminates a process for a specified agent pool.
5251
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerService/managedclusters/{resourceName}/agentPools/{agentPoolName}/abort
5352
```
5453

55-
The following example terminates a process for a specified managed cluster.
54+
The following example terminates a process for a specified cluster.
5655

5756
```rest
5857
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerService/managedclusters/{resourceName}/abort

0 commit comments

Comments
 (0)