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/kubernetes-walkthrough.md
+7-9Lines changed: 7 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: iainfoulds
6
6
7
7
ms.service: container-service
8
8
ms.topic: quickstart
9
-
ms.date: 05/31/2019
9
+
ms.date: 05/20/2019
10
10
ms.author: iainfou
11
11
ms.custom: H1Hack27Feb2017, mvc, devcenter
12
12
@@ -54,7 +54,7 @@ The following example output shows the resource group created successfully:
54
54
}
55
55
```
56
56
57
-
## Create AKS cluster
57
+
## Create an AKS cluster
58
58
59
59
Use the [az aks create][az-aks-create] command to create an AKS cluster. The following example creates a cluster named *myAKSCluster* with one node. Azure Monitor for containers is also enabled using the *--enable-addons monitoring* parameter.
60
60
@@ -236,11 +236,11 @@ To see the Azure Vote app in action, open a web browser to the external IP addre
236
236
237
237
When the AKS cluster was created, Azure Monitor for containers was enabled to capture health metrics for both the cluster nodes and pods. These health metrics are available in the Azure portal.
238
238
239
-
To see current status, uptime, and resource usage for the Azure Vote pods, complete the following steps:
239
+
To see the current status, uptime, and resource usage for the Azure Vote pods, complete the following steps:
240
240
241
241
1. Open a web browser to the Azure portal [https://portal.azure.com][azure-portal].
242
242
1. Select your resource group, such as *myResourceGroup*, then select your AKS cluster, such as *myAKSCluster*.
243
-
1.In the **Monitoring** group on the left-hand side, choose **Insights**
243
+
1.Under **Monitoring** on the left-hand side, choose **Insights**
244
244
1. Across the top, choose to **+ Add Filter**
245
245
1. Select *Namespace* as the property, then choose *\<All but kube-system\>*
246
246
1. Choose to view the **Containers**.
@@ -249,15 +249,13 @@ The *azure-vote-back* and *azure-vote-front* containers are displayed, as shown
249
249
250
250

251
251
252
-
To see logs for the `azure-vote-front` pod, click on that container and change the dropdown on the right (you may need to scroll the window to the right to it) from **View in analytics** to **View container logs**. These logs include the *stdout* and *stderr* streams from the container.
253
-
254
-
Click **Run** to see the logs. You can view a log by opening its entry in the list.
252
+
To see logs for the `azure-vote-back` pod, choose the option to **View in analytics**, then click the **View container logs** link on the right-hand side of the containers list. These logs include the *stdout* and *stderr* streams from the container.
255
253
256
254

257
255
258
-
## Delete cluster
256
+
## Delete the cluster
259
257
260
-
When you no longer need the cluster, use the [az group delete][az-group-delete] command to remove the resource group, container service, and all related resources.
258
+
When the cluster is no longer needed, use the [az group delete][az-group-delete] command to remove the resource group, container service, and all related resources.
261
259
262
260
```azurecli-interactive
263
261
az group delete --name myResourceGroup --yes --no-wait
0 commit comments