From ca3f05a593e39f20527496cfbee58a833c287b91 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Adam=20=C5=BBmuda?= Date: Fri, 10 Jun 2022 10:24:53 +0200 Subject: [PATCH 1/5] Change right click to click in LAB 2a and 2b --- Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md | 2 +- Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md index 9b697387..baef1e82 100644 --- a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md +++ b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md @@ -200,7 +200,7 @@ In this task, you will create an Azure Active Directory user, assign the RBAC ro 1. Select **Refresh** to verify that the subscription has successfully moved to the **Tenant Root management group**. -1. Navigate back to the **Management groups** blade, right click the **ellipsis** icon to the right of the **az104-02-mg1** management group and click **Delete**. +1. Navigate back to the **Management groups** blade, click the **ellipsis** icon to the right of the **az104-02-mg1** management group and click **Delete**. #### Review diff --git a/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md b/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md index e3f3abcb..b090ecce 100644 --- a/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md +++ b/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md @@ -144,7 +144,7 @@ In this task, we will use a different policy definition to remediate any non-com 1. In the **Authoring** section, click **Assignments**. -1. In the list of assignments, right click the ellipsis icon in the row representing the **Require Role tag with Infra value** policy assignment and use the **Delete assignment** menu item to delete the assignment. +1. In the list of assignments, click the ellipsis icon in the row representing the **Require Role tag with Infra value** policy assignment and use the **Delete assignment** menu item to delete the assignment. 1. Click **Assign policy** and specify the **Scope** by clicking the ellipsis button and selecting the following values: From 56e1ed2f4ae4b1780f0812ea8ecc4af617e0e6f7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Adam=20=C5=BBmuda?= Date: Fri, 10 Jun 2022 10:25:27 +0200 Subject: [PATCH 2/5] Changed wording to match Portal UI in Lab 6 Task 3 --- .../Labs/LAB_06-Implement_Network_Traffic_Management.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md index 7e0c4370..8e8ec1f8 100644 --- a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md +++ b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md @@ -322,7 +322,7 @@ In this task, you will configure and test routing between the two spoke virtual | --- | --- | | Route name | **az104-06-route-vnet2-to-vnet3** | | Address prefix destination | **IP Addresses** | - | Source IP addresses/CIDR ranges | **10.63.0.0/20** | + | Destination IP addresses/CIDR ranges | **10.63.0.0/20** | | Next hop type | **Virtual appliance** | | Next hop address | **10.60.0.4** | @@ -365,7 +365,7 @@ In this task, you will configure and test routing between the two spoke virtual | --- | --- | | Route name | **az104-06-route-vnet3-to-vnet2** | | Address prefix destination | **IP Addresses** | - | Source IP addresses/CIDR ranges | **10.62.0.0/20** | + | Destination IP addresses/CIDR ranges | **10.62.0.0/20** | | Next hop type | **Virtual appliance** | | Next hop address | **10.60.0.4** | From 0b27cf5592b58cc2f49560e371cbba71c684c4de Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Adam=20=C5=BBmuda?= Date: Fri, 10 Jun 2022 10:29:06 +0200 Subject: [PATCH 3/5] Changed wording to match Portal UI in Lab 7 Task 2 --- Instructions/Labs/LAB_07-Manage_Azure_Storage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md index 4881db83..d59260fe 100644 --- a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md +++ b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md @@ -106,7 +106,7 @@ In this task, you will create and configure an Azure Storage account. 1. Click **Next: Advanced >**, on the **Advanced** tab of the **Create storage account** blade, review the available options, accept the defaults, and click **Next: Networking >**. -1. On the **Networking** tab of the **Create storage account** blade, review the available options, accept the default option **Public endpoint (all networks}** and click **Next: Data protection >**. +1. On the **Networking** tab of the **Create storage account** blade, review the available options, accept the default option **Enable public access from all networks** and click **Next: Data protection >**. 1. On the **Data protection** tab of the **Create storage account** blade, review the available options, accept the defaults, click **Review + Create**, wait for the validation process to complete and click **Create**. From 7bf7f2078245a51ebe8feba815dd1c60c5612991 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Adam=20=C5=BBmuda?= Date: Fri, 10 Jun 2022 12:30:27 +0200 Subject: [PATCH 4/5] Changed wording to match Portal UI in Lab 8 Task 1 --- Instructions/Labs/LAB_08-Manage_Virtual_Machines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md index 6519b149..a5bc1b01 100644 --- a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md +++ b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md @@ -40,7 +40,7 @@ In this task, you will deploy Azure virtual machines into different availability 1. Sign in to the [Azure portal](http://portal.azure.com). -1. In the Azure portal, search for and select **Virtual machines** and, on the **Virtual machines** blade, click **+ Create**, click **+ Virtual machine**. +1. In the Azure portal, search for and select **Virtual machines** and, on the **Virtual machines** blade, click **+ Create**, click **+ Azure virtual machine**. 1. On the **Basics** tab of the **Create a virtual machine** blade, specify the following settings (leave others with their default values): From 4354b1a0e31dafa2b3ddc996859a4be7472e03d9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Adam=20=C5=BBmuda?= Date: Fri, 10 Jun 2022 13:20:42 +0200 Subject: [PATCH 5/5] Regroup dependant commands in Lab 9c task 4 together --- .../Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md b/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md index e93675a5..ea647d71 100644 --- a/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md +++ b/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md @@ -173,11 +173,6 @@ In this task, you will scale horizontally the number of pods and then number of 1. From the **Cloud Shell** pane, and run the following to scale the deployment by increasing of the number of pods to 2: ```sh - - RESOURCE_GROUP='az104-09c-rg1' - - AKS_CLUSTER='az104-9c-aks1' - kubectl scale --replicas=2 deployment/nginx-deployment ``` @@ -192,6 +187,10 @@ In this task, you will scale horizontally the number of pods and then number of 1. From the **Cloud Shell** pane, run the following to scale out the cluster by increasing the number of nodes to 2: ```sh + RESOURCE_GROUP='az104-09c-rg1' + + AKS_CLUSTER='az104-9c-aks1' + az aks scale --resource-group $RESOURCE_GROUP --name $AKS_CLUSTER --node-count 2 ```