From 52c4be38019f38f54fd1c4f894a57fd55e1aef7b Mon Sep 17 00:00:00 2001 From: Unai Huete Beloki Date: Thu, 14 Jan 2021 07:29:53 +0100 Subject: [PATCH 01/14] typo --- ..._multi-container_application_to_Azure_Kubernetes_Services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md index 694e11893..6726e6209 100644 --- a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md +++ b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md @@ -94,7 +94,7 @@ In this task, you will use Azure CLI to perform deployment of the Azure resource >**Note**: If this is the first time you are starting **Cloud Shell** and you are presented with the **You have no storage mounted** message, select the subscription you are using in this lab, and select **Create storage**. -1. From the Bash session in the Cloud Shell pane, run the following to identify the latest version of Kubernetes available in the Azure region you will be using in this lab (replace the `` placeholder with the name of the Azure region where you intend to deploy resources in this lab): ```bash LOCATION= From 8880e2006f592f46c808e81c733f64a931b32915 Mon Sep 17 00:00:00 2001 From: Unai Huete Beloki Date: Thu, 14 Jan 2021 07:31:09 +0100 Subject: [PATCH 02/14] clariffy possible regions --- ..._multi-container_application_to_Azure_Kubernetes_Services.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md index 6726e6209..7f1889571 100644 --- a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md +++ b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md @@ -96,6 +96,8 @@ In this task, you will use Azure CLI to perform deployment of the Azure resource 1. From the Bash session in the Cloud Shell pane, run the following to identify the latest version of Kubernetes available in the Azure region you will be using in this lab (replace the `` placeholder with the name of the Azure region where you intend to deploy resources in this lab): + > **Note**: possible locations can be found by running the following command, use the **Name** property on `` : `az account list-locations -o table` + ```bash LOCATION= VERSION=$(az aks get-versions --location $LOCATION --query 'orchestrators[-1].orchestratorVersion' --output tsv) From 7a3fb1ffe6b472ca9a1cb5cb9dd50c530ee65796 Mon Sep 17 00:00:00 2001 From: Unai Huete Beloki Date: Thu, 14 Jan 2021 07:32:09 +0100 Subject: [PATCH 03/14] project name was missing --- ..._multi-container_application_to_Azure_Kubernetes_Services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md index 7f1889571..5f1257473 100644 --- a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md +++ b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md @@ -66,7 +66,7 @@ In this task, you will use Azure DevOps Demo Generator to generate a new project 1. Click **Sign in** and sign in using the Microsoft account associated with your Azure DevOps subscription. 1. If required, on the **Azure DevOps Demo Generator** page, click **Accept** to accept the permission requests for accessing your Azure DevOps subscription. -1. On the **Create New Project** page, in the **New Project Name** textbox, type ***, in the **Select organization** dropdown list, select your Azure DevOps organization, and then click **Choose template**. +1. On the **Create New Project** page, in the **New Project Name** textbox, type **Deploying a multi-container application to AKS**, in the **Select organization** dropdown list, select your Azure DevOps organization, and then click **Choose template**. 1. In the list of templates, in the toolbar, click **DevOps Labs**, select the **Azure Kubernetes Service** template and click **Select Template**. 1. Back on the **Create New Project** page, if prompted to install a missing extension, select the checkbox below the **Replace Tokens** and **Kubernetes extension** labels and click **Create Project**. From 5a7697419560c6f8697d7503547bf01b37f4119e Mon Sep 17 00:00:00 2001 From: Unai Huete Beloki Date: Thu, 14 Jan 2021 07:36:19 +0100 Subject: [PATCH 04/14] make sure they use Bash --- ..._multi-container_application_to_Azure_Kubernetes_Services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md index 5f1257473..02623d52c 100644 --- a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md +++ b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md @@ -94,7 +94,7 @@ In this task, you will use Azure CLI to perform deployment of the Azure resource >**Note**: If this is the first time you are starting **Cloud Shell** and you are presented with the **You have no storage mounted** message, select the subscription you are using in this lab, and select **Create storage**. -1. From the Bash session in the Cloud Shell pane, run the following to identify the latest version of Kubernetes available in the Azure region you will be using in this lab (replace the `` placeholder with the name of the Azure region where you intend to deploy resources in this lab): +1. From the **Bash** session in the Cloud Shell pane, run the following to identify the latest version of Kubernetes available in the Azure region you will be using in this lab (replace the `` placeholder with the name of the Azure region where you intend to deploy resources in this lab): > **Note**: possible locations can be found by running the following command, use the **Name** property on `` : `az account list-locations -o table` From 7af9c846aa737c5b63274df46fbf52743f94400d Mon Sep 17 00:00:00 2001 From: Unai Huete Beloki Date: Thu, 14 Jan 2021 07:45:49 +0100 Subject: [PATCH 05/14] fix link --- ..._multi-container_application_to_Azure_Kubernetes_Services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md index 02623d52c..fbdb79f53 100644 --- a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md +++ b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md @@ -62,7 +62,7 @@ In this task, you will use Azure DevOps Demo Generator to generate a new project 1. On your lab computer, start a web browser and navigate to [Azure DevOps Demo Generator](https://azuredevopsdemogenerator.azurewebsites.net). This utility site will automate the process of creating a new Azure DevOps project within your account that is prepopulated with content (work items, repos, etc.) required for the lab. - > **Note**: For more information on the site, see https://docs.microsoft.com/en-us/azure/devops/demo-gen. + > **Note**: For more information on the site, see [https://docs.microsoft.com/en-us/azure/devops/demo-gen](https://docs.microsoft.com/en-us/azure/devops/demo-gen) . 1. Click **Sign in** and sign in using the Microsoft account associated with your Azure DevOps subscription. 1. If required, on the **Azure DevOps Demo Generator** page, click **Accept** to accept the permission requests for accessing your Azure DevOps subscription. From 4283d9d30632b71f811f208044180fd57620e45c Mon Sep 17 00:00:00 2001 From: Unai Huete Beloki Date: Thu, 14 Jan 2021 07:46:39 +0100 Subject: [PATCH 06/14] provide example region --- ..._multi-container_application_to_Azure_Kubernetes_Services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md index fbdb79f53..5eca75508 100644 --- a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md +++ b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md @@ -94,7 +94,7 @@ In this task, you will use Azure CLI to perform deployment of the Azure resource >**Note**: If this is the first time you are starting **Cloud Shell** and you are presented with the **You have no storage mounted** message, select the subscription you are using in this lab, and select **Create storage**. -1. From the **Bash** session in the Cloud Shell pane, run the following to identify the latest version of Kubernetes available in the Azure region you will be using in this lab (replace the `` placeholder with the name of the Azure region where you intend to deploy resources in this lab): +1. From the **Bash** session in the Cloud Shell pane, run the following to identify the latest version of Kubernetes available in the Azure region you will be using in this lab (replace the `` placeholder with the name of the Azure region where you intend to deploy resources in this lab, for example `eastus`): > **Note**: possible locations can be found by running the following command, use the **Name** property on `` : `az account list-locations -o table` From ac050d0718bf69c217a624fbfdf027c9df624d98 Mon Sep 17 00:00:00 2001 From: Unai Huete Beloki Date: Thu, 14 Jan 2021 07:49:57 +0100 Subject: [PATCH 07/14] clariffy --- ..._multi-container_application_to_Azure_Kubernetes_Services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md index 5eca75508..1b23e115e 100644 --- a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md +++ b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md @@ -94,7 +94,7 @@ In this task, you will use Azure CLI to perform deployment of the Azure resource >**Note**: If this is the first time you are starting **Cloud Shell** and you are presented with the **You have no storage mounted** message, select the subscription you are using in this lab, and select **Create storage**. -1. From the **Bash** session in the Cloud Shell pane, run the following to identify the latest version of Kubernetes available in the Azure region you will be using in this lab (replace the `` placeholder with the name of the Azure region where you intend to deploy resources in this lab, for example `eastus`): +1. From the **Bash** session in the Cloud Shell pane, run the following to identify the latest version of Kubernetes available in the Azure region you will be using in this lab ( **replace the `` placeholder** with the name of the Azure region where you intend to deploy resources in this lab, we could `eastus` as default option): > **Note**: possible locations can be found by running the following command, use the **Name** property on `` : `az account list-locations -o table` From 6318bf5ddfcf121fd620ea67f0ac90084b05addb Mon Sep 17 00:00:00 2001 From: Unai Huete Beloki Date: Thu, 14 Jan 2021 07:50:22 +0100 Subject: [PATCH 08/14] my typo --- ..._multi-container_application_to_Azure_Kubernetes_Services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md index 1b23e115e..521420c34 100644 --- a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md +++ b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md @@ -94,7 +94,7 @@ In this task, you will use Azure CLI to perform deployment of the Azure resource >**Note**: If this is the first time you are starting **Cloud Shell** and you are presented with the **You have no storage mounted** message, select the subscription you are using in this lab, and select **Create storage**. -1. From the **Bash** session in the Cloud Shell pane, run the following to identify the latest version of Kubernetes available in the Azure region you will be using in this lab ( **replace the `` placeholder** with the name of the Azure region where you intend to deploy resources in this lab, we could `eastus` as default option): +1. From the **Bash** session in the Cloud Shell pane, run the following to identify the latest version of Kubernetes available in the Azure region you will be using in this lab ( **replace the `` placeholder** with the name of the Azure region where you intend to deploy resources in this lab, we could use `eastus` as default option): > **Note**: possible locations can be found by running the following command, use the **Name** property on `` : `az account list-locations -o table` From 453ccda4dc1f45b8c877cc36a3121cdea9e2b1d5 Mon Sep 17 00:00:00 2001 From: Unai Huete Beloki Date: Thu, 14 Jan 2021 07:52:44 +0100 Subject: [PATCH 09/14] index fix --- ...ainer_application_to_Azure_Kubernetes_Services.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md index 521420c34..1c6e9a204 100644 --- a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md +++ b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md @@ -96,13 +96,13 @@ In this task, you will use Azure CLI to perform deployment of the Azure resource 1. From the **Bash** session in the Cloud Shell pane, run the following to identify the latest version of Kubernetes available in the Azure region you will be using in this lab ( **replace the `` placeholder** with the name of the Azure region where you intend to deploy resources in this lab, we could use `eastus` as default option): - > **Note**: possible locations can be found by running the following command, use the **Name** property on `` : `az account list-locations -o table` + > **Note**: possible locations can be found by running the following command, use the **Name** property on `` : `az account list-locations -o table` + + ```bash + LOCATION= + VERSION=$(az aks get-versions --location $LOCATION --query 'orchestrators[-1].orchestratorVersion' --output tsv) + ``` - ```bash - LOCATION= - VERSION=$(az aks get-versions --location $LOCATION --query 'orchestrators[-1].orchestratorVersion' --output tsv) - ``` - 1. From the Bash session in the Cloud Shell pane, run the following to create a resource group that will host the AKS deployment: ```bash From f68326680a41feefbc589ab6d720ce99a9053fbf Mon Sep 17 00:00:00 2001 From: Unai Huete Beloki Date: Thu, 14 Jan 2021 08:21:09 +0100 Subject: [PATCH 10/14] typing ACR name does not work! --- ...ulti-container_application_to_Azure_Kubernetes_Services.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md index 1c6e9a204..23c60e829 100644 --- a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md +++ b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md @@ -188,8 +188,8 @@ select the entry representing the Azure subscription you are using in this lab, >**Note**: This step creates an Azure service connection, which defines and secures a connection to the target Azure subscription, using Service Principal Authentication (SPA). -1. In the list of tasks of the pipeline, with the **Run services** task selected, on the **Docker Compose** pane on the right side, in the **Azure Container Registry** dropdown list, select the entry representing the ACR instance you created earlier in this lab. -1. Repeat the previous two steps to configure the **Azure subscription** and **Azure Container Registry** settings in the **Build services**, **Push services**, and **Lock services** tasks, but instead of selecting your Azure subscription in this case, select the newly created service connection. +1. In the list of tasks of the pipeline, with the **Run services** task selected, on the **Docker Compose** pane on the right side, in the **Azure Container Registry** dropdown list, select the entry representing the ACR instance you created earlier in this lab (**Refresh the list if needed, typing out the ACR name does not work!**). +1. Repeat the previous two steps to configure the **Azure subscription** (next time do not Authorize again, use the created **Available Azure service connections** ) and **Azure Container Registry** settings in the **Build services**, **Push services**, and **Lock services** tasks, but instead of selecting your Azure subscription in this case, select the newly created service connection. >**Note**: The pipeline consists of the following tasks From 146a59460f665c6b81bca9be3963b43e7bd9cd77 Mon Sep 17 00:00:00 2001 From: Unai Huete Beloki Date: Thu, 14 Jan 2021 08:27:38 +0100 Subject: [PATCH 11/14] agent pool selection --- ...ulti-container_application_to_Azure_Kubernetes_Services.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md index 23c60e829..30935042a 100644 --- a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md +++ b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md @@ -206,6 +206,7 @@ select the entry representing the Azure subscription you are using in this lab, 1. In the web browser window displaying the Azure DevOps portal, in the vertical menu bar at the far left of the Azure DevOps portal, in the **Pipelines** section, click **Releases**. 1. On the **Pipelines / Releases** pane, select the **MyHealth.AKS.Release** entry and click **Edit**. 1. On the **All pipelines / MyHealth.AKS.Release** pane, in the rectangle representing the **Dev** stage of the deployment, click the **2 jobs, 3 tasks** link. +1. For the **DB deployment** job and **AKS deployment** (by clicking on those names) , choose "Agent Pool" **Azure Pipelines --> windows-2019**. 1. In the list of tasks of the **Dev** stage, within the **DB deployment** job section, select the **Execute Azure SQL: DacpacTask** task and, on the **Azure SQL Database deployment** pane on the right side, in the **Azure Subscription** dropdown list, select the entry representing the Azure service connection you created earlier in this task. 1. In the list of tasks of the **Dev** stage, in the **AKS deployment** job section, select the **Create Deployments & Services in AKS** task. 1. On the **Kubectl** pane on the right side, in the **Azure Subscription** dropdown list, select the entry representing the same Azure service connection, in the **Resource group** dropdown list, select the **az400m16l01a-RG** entry, and in the **Kubernetes cluster** dropdown list, select the entry representing the AKS cluster you deployed earlier in this lab. @@ -225,9 +226,6 @@ select the entry representing the Azure subscription you are using in this lab, >**Note**: In the list of pipeline variables, **DatabaseName** is set to **mhcdb**, **SQLuser** is set to **sqladmin**, and **SQLpassword** is set to **P2ssw0rd1234**. If you entered different values when creating the Azure SQL database earlier in this lab, update the values of the variables accordingly. -1. For the **DB deployment** job and **AKS deployment** , choose "Agent Pool" **Azure Pipelines --> windows-2019**. - - #### Task 3: Trigger the build and release pipelines In this task, you will trigger the build and release pipelines and validate their completion. From ab412df2d5097e30bd3ca443527bdb8ef385e546 Mon Sep 17 00:00:00 2001 From: Unai Huete Beloki Date: Thu, 14 Jan 2021 08:28:33 +0100 Subject: [PATCH 12/14] typo --- ..._multi-container_application_to_Azure_Kubernetes_Services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md index 30935042a..e1a713583 100644 --- a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md +++ b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md @@ -206,7 +206,7 @@ select the entry representing the Azure subscription you are using in this lab, 1. In the web browser window displaying the Azure DevOps portal, in the vertical menu bar at the far left of the Azure DevOps portal, in the **Pipelines** section, click **Releases**. 1. On the **Pipelines / Releases** pane, select the **MyHealth.AKS.Release** entry and click **Edit**. 1. On the **All pipelines / MyHealth.AKS.Release** pane, in the rectangle representing the **Dev** stage of the deployment, click the **2 jobs, 3 tasks** link. -1. For the **DB deployment** job and **AKS deployment** (by clicking on those names) , choose "Agent Pool" **Azure Pipelines --> windows-2019**. +1. For the **DB deployment** job and **AKS deployment** job (by clicking on those names) , choose "Agent Pool" **Azure Pipelines --> windows-2019**. 1. In the list of tasks of the **Dev** stage, within the **DB deployment** job section, select the **Execute Azure SQL: DacpacTask** task and, on the **Azure SQL Database deployment** pane on the right side, in the **Azure Subscription** dropdown list, select the entry representing the Azure service connection you created earlier in this task. 1. In the list of tasks of the **Dev** stage, in the **AKS deployment** job section, select the **Create Deployments & Services in AKS** task. 1. On the **Kubectl** pane on the right side, in the **Azure Subscription** dropdown list, select the entry representing the same Azure service connection, in the **Resource group** dropdown list, select the **az400m16l01a-RG** entry, and in the **Kubernetes cluster** dropdown list, select the entry representing the AKS cluster you deployed earlier in this lab. From d0b3c39f2e8e803116e3a3683e41bf7ef66ee721 Mon Sep 17 00:00:00 2001 From: Unai Huete Beloki Date: Thu, 14 Jan 2021 12:00:12 +0100 Subject: [PATCH 13/14] removed eastus --> Michael comment --- ..._multi-container_application_to_Azure_Kubernetes_Services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md index e1a713583..b09564b9f 100644 --- a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md +++ b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md @@ -94,7 +94,7 @@ In this task, you will use Azure CLI to perform deployment of the Azure resource >**Note**: If this is the first time you are starting **Cloud Shell** and you are presented with the **You have no storage mounted** message, select the subscription you are using in this lab, and select **Create storage**. -1. From the **Bash** session in the Cloud Shell pane, run the following to identify the latest version of Kubernetes available in the Azure region you will be using in this lab ( **replace the `` placeholder** with the name of the Azure region where you intend to deploy resources in this lab, we could use `eastus` as default option): +1. From the **Bash** session in the Cloud Shell pane, run the following to identify the latest version of Kubernetes available in the Azure region you will be using in this lab ( **replace the `` placeholder** with the name of the Azure region where you intend to deploy resources in this lab): > **Note**: possible locations can be found by running the following command, use the **Name** property on `` : `az account list-locations -o table` From deeff4581a361db16612b990df2f9b2e5859a92c Mon Sep 17 00:00:00 2001 From: Unai Huete Beloki Date: Thu, 14 Jan 2021 12:12:27 +0100 Subject: [PATCH 14/14] =?UTF-8?q?Michael=C2=B4s=20first=20comment=20to=20s?= =?UTF-8?q?eparate=20commands?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- ...lti-container_application_to_Azure_Kubernetes_Services.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md index b09564b9f..79d583d7c 100644 --- a/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md +++ b/Instructions/Labs/AZ400_M16_Deploying_multi-container_application_to_Azure_Kubernetes_Services.md @@ -96,10 +96,13 @@ In this task, you will use Azure CLI to perform deployment of the Azure resource 1. From the **Bash** session in the Cloud Shell pane, run the following to identify the latest version of Kubernetes available in the Azure region you will be using in this lab ( **replace the `` placeholder** with the name of the Azure region where you intend to deploy resources in this lab): + ```bash + LOCATION= + ``` + > **Note**: possible locations can be found by running the following command, use the **Name** property on `` : `az account list-locations -o table` ```bash - LOCATION= VERSION=$(az aks get-versions --location $LOCATION --query 'orchestrators[-1].orchestratorVersion' --output tsv) ```