diff --git a/New Instructions/Lab/LAB_09b-Implement_Azure_Containers.md b/New Instructions/Lab/LAB_09b-Implement_Azure_Containers.md index d7f074a0..fc745f87 100644 --- a/New Instructions/Lab/LAB_09b-Implement_Azure_Containers.md +++ b/New Instructions/Lab/LAB_09b-Implement_Azure_Containers.md @@ -11,7 +11,7 @@ lab: In this lab, you learn how to implement Azure Container Instances and Azure Container Apps. You learn to deploy an Azure Container Instance to display a Hello World app. You learn to deploy the default Azure Container App. -This lab requires an Azure subscription. Your subscription type may affect the availability of features in this lab. You may change the region, but the steps are written using East US. +This lab requires an Azure subscription. Your subscription type may affect the availability of features in this lab. You may change the region, but the steps are written using **East US**. ## Estimated timing: 30 minutes @@ -49,14 +49,14 @@ In this task, you will create a new container instance for the web application. | Setting | Value | | ---- | ---- | - | Subscription | the name of your Azure subscription | + | Subscription | Select your Azure subscription | | Resource group | `az104-rg9` (If necessary, select **Create new**) | | Container name | `az104-c1` | | Region | **East US** (or a region available near you)| | Image Source | **Quickstart images** | | Image | **mcr.microsoft.com/azuredocs/aci-helloworld:latest (Linux)** | -1. Click **Next: Networking >** and, on the **Networking** tab of the **Create container instance** blade, specify the following settings (leave others with their default values): +1. Click **Next: Networking >** and specify the following settings (leave others with their default values): | Setting | Value | | --- | --- | @@ -64,13 +64,13 @@ In this task, you will create a new container instance for the web application. >**Note**: Your container will be publicly reachable at dns-name-label.region.azurecontainer.io. If you receive a **DNS name label not available** error message, specify a different value. -1. Click **Next: Advanced >**, review the settings on the **Advanced** tab of the **Create container instance** blade without making any changes. +1. Click **Next: Advanced >**, review the settings without making any changes. 1. Click **Review + Create**, ensure that the validation passed and then select **Create**. >**Note**: Wait for the deployment to complete. This should take 2-3 minutes. - >**Note**: While you wait, you may be interested in viewing the [code behind the sample application](https://github.com/Azure-Samples/aci-helloworld). To view it, browse the \\app folder. + >**Note**: While you wait, you may be interested in viewing the [code behind the sample application](https://github.com/Azure-Samples/aci-helloworld). To view the code, browse the \\app folder. ## Task 2: Review the functionality of the Azure Container Instance @@ -84,9 +84,9 @@ In this task, you will review the deployment of the container instance. By defau ![Screenshot of the ACI overview page in the portal.](../media/az104-lab09b-aci-overview.png) -1. Verify that the **Welcome to Azure Container Instance** page is displayed. +1. Verify that the **Welcome to Azure Container Instance** page is displayed. Refresh the page several times to create some log entries then close the browser tab. -1. Close the new browser tab, back in the Azure portal, in the **Settings** section of the container instance blade, click **Containers**, and then click **Logs**. +1. In the **Settings** section of the container instance blade, click **Containers**, and then click **Logs**. 1. Verify that you see the log entries representing the HTTP GET request generated by displaying the application in the browser. @@ -102,7 +102,7 @@ Azure Container Apps take the concept of a managed Kubernetes cluster a step fur 1. From **Container Apps**, select **Create**. -1. Use the following information to fill out the details on the **Basics** tab, then select **Next: Container >**. +1. Use the following information to fill out the details on the **Basics** tab.*. | Setting | Action | |---|---| @@ -112,15 +112,11 @@ Azure Container Apps take the concept of a managed Kubernetes cluster a step fur | Region | **East US** (Or a region available near you) | | Container Apps Environment | Leave default | -1. Ensure that **Use quickstart image** is enabled and that the quickstart image is set to **Simple hello world container**. +1. On the **Container** tab, ensure that **Use quickstart image** is enabled and that the quickstart image is set to **Simple hello world container**. -1. Select the **Review and create** button at the bottom of the page. +1. Select the **Review and create** and then **Create**. - >**Note**: If there are errors, any tab containing errors is marked with a red dot. Navigate to the appropriate tab. Fields containing an error will be highlighted in red. Once all errors are fixed, select **Review and create** again. - -1. Select **Create**. - - >**Note:** A page with the message *Deployment is in progress* is displayed. Once the deployment is successfully completed, you'll see the message: *Your deployment is complete*. + >**Note:** Wait for the container app to deploy. This will take a couple of minutes. ## Task 4: Test and verify deployment of the container app @@ -140,7 +136,7 @@ Congratulations on completing the lab. Here are the main takeaways for this lab. + Azure Container Instances (ACI) is a service that enables you to deploy containers on the Microsoft Azure public cloud. ACI doesn't require you to provision or manage any underlying infrastructure. The service supports both Linux containers and Windows containers. + Azure Container Apps (ACA) is a serverless platform that allows you to maintain less infrastructure and save costs while running containerized applications. Instead of worrying about server configuration, container orchestration, and deployment details, Container Apps provides all the up-to-date server resources required to keep your applications stable and secure. -+ Workloads on ACI are usually started and stopped by some kind of process or trigger and are usually short-lived. Workloads on ACA are usually long-running processes like a Web app. ++ Workloads on ACI are usually started and stopped by some kind of process or trigger and are usually short-lived. Workloads on ACA are usually long-running processes like a Web App. ## Cleanup your resources