Lab: Deploy and manage a container app using Azure Container Apps

Student lab answer key

Instructions

In this lab, you’ll deploy and manage an app using Azure Container Apps. To implement the solution, you begin by configuring a development environment that uses a combination of local tools and Azure resources. Once the environment is prepared, you use Azure Container Registry, Azure Container Apps, and Azure Pipelines to deploy and manage your app.

By the end of this lab, you’re able to:

Configure a secure connection between an Azure Container Registry and an Azure Container Apps.
Create and configure a container app in Azure Container Apps.
Configure continuous integration by using Azure Pipelines.
Scale a deployed app in Azure Container Apps.
Manage revisions in Azure Container Apps.

Exercise 1: Configure Azure resources

In this exercise, you’ll configure Azure resources that support your Azure Container Apps solution.

It will take about 10-15 minutes to complete the following tasks:

Examine resource group settings.
Configure an Azure Virtual Network with subnets.
Configure an Azure Service Bus resource.
Configure an Azure Container Registry resource.

Task 1: Examine resource group settings

Complete the following steps to examine the location setting of the resource group that’s used in this lab.

In the lab environment, open a browser window, and then navigate to the Azure portal: https://portal.azure.com/

Work with your classroom instructor if need help signing into the Azure portal with a subscription/account that’s appropriate for this lab.
On your Azure portal Home page, under Navigate, select Resource groups.
On the Resource groups page, select RG1.

If the RG1 resource group has not been created, create it now.
Make note of the Location setting assigned to the RG1 resource group.

You will use the same location/region when creating other Azure resources during this lab.
Close the RG1 page, and then close the Resource groups page.

Task 2: Configure a Virtual Network and subnets

Complete the following steps to configure a virtual network and subnets.

On the top search bar of the Azure portal, in the Search textbox, enter virtual network
In the search results, select Virtual networks.
Select Create virtual network.
On the Basics tab, configure your virtual network as follows:
- Subscription: Ensure that the Azure subscription that you’re using for this guided project is selected.
- Resource group name: Select RG1
- Virtual network name: Enter VNET1
- Region: Ensure that the specified Region matches the location setting of your resource group.
Select the IP addresses tab.
On the IP addresses tab, under Subnets, select default.
On the Edit subnet page, configure the subnet as follows:
- Name: Enter PESubnet
- Starting address: Ensure that 10.0.0.0 is specified.
- Subnet size: Ensure that /24 (256 addresses) is specified.
This first subnet will be used for a private endpoint (Azure Container Registry).
Select Save.
On the IP addresses tab, select + Add a subnet.
On the Add a subnet page, configure the subnet as follows:
- Name: Enter ACASubnet
- Starting address: Ensure that 10.0.4.0 is specified.
- Subnet size: Ensure that /23 (512 addresses) is specified.
The subnet for Azure Container Apps requires an address space larger than 256.
Select Add.
Select Review + create.
Once validation has passed, select Create.
Wait for the deployment to complete, and then close the VNET1 page.

Task 3: Configure Service Bus

Complete the following steps to configure a Service Bus instance.

On the top search bar of the Azure portal, in the Search textbox, enter service bus
In the search results, select Service Bus.
Select Create service bus namespace.
On the Basics tab, configure your Service bus namespace as follows:
- Subscription: Ensure that the Azure subscription that you’re using for this guided project is selected.
- Resource group name: Select RG1
- Namespace name: Enter sb-az2003- followed by your initials and the date. For example: sb-az2003-cah12oct.
- Location: Ensure that specified Location matches the location setting of your resource group.
- Pricing tier: Select Basic.
Select Review + create.
Once the Validation succeeded message appears, select Create.
Wait for the deployment to complete, and then close the Service Bus Namespace page.

Task 4: Configure Azure Container Registry

Complete the following steps to configure a Container Registry instance.

On the top search bar of the Azure portal, in the Search textbox, enter container registry
In the search results, select Container registries.
On the Container registries page, select Create container registry or + Create.
On the Basic tab of the Create container registry page, specify the following information:

[!NOTE] The name of your Registry must be unique. Also, the Premium tier is required for private link with private endpoints.
- Subscription: Ensure that the Azure subscription that you’re using for this guided project is selected.
- Resource group: Select RG1.
- Registry name: Enter acraz2003 followed by your initials and date. For example: acraz2003cah12oct
- Location: Ensure that specified Location matches the location setting of your resource group.
- SKU: Select Premium.
Select Review + create.
Once the Validation passed message appears, select Create.
After the deployment has completed, open your Container registry resource.
On the left-side menu of the Container registry page, under Settings, select Networking.
On the Networking page, on the Public access tab, ensure that All networks is selected.
On the left-side menu, under Settings, select Properties.
On the Properties page, select Admin user, and then select Save.
Close the Container registry page.
Close your Azure portal (browser) window.

Exercise 2: Configure developer tools in the host environment

In this exercise, you ensure that scripting and developer tools are configured correctly on the virtual machine.

It will take about 20-25 minutes to complete the following tasks:

Configure Azure CLI extensions.
Install Docker Desktop.
Install the .NET 8 SDK.
Update Visual Studio Code and configure extensions.

Task 1: Uninstall Visual Studio Code

Complete the following steps to uninstall Visual Studio Code.

Open the Windows Start menu.
On the Start menu, select Settings.
On the left side menu, select Apps, and then select Installed Apps.
Locate Microsoft Visual Studio Code.
To the right of Microsoft Visual Studio Code, select the ellipsis (…), and then select Uninstall.
In the popup window, select Uninstall.
When prompted, select Yes and then select Ok.
Close Settings.

Task 2: Configure Azure CLI extensions

Complete the following steps to configure Azure CLI.

Open a command line or terminal application, such as Windows Command Prompt.
Sign in to Azure using the az login command.

A browser window will open that allows you to select the Azure account.
Follow the prompts to complete the authentication process.
Close the browser window.
In the command line app, to install the Azure Container Apps extension, enter the following command: az extension add --name containerapp --upgrade
Close the command line app.

Task 3: Install Docker Desktop

Complete the following steps to install Docker Desktop.

Open a browser window, and then navigate to the Docker Desktop install page: https://docs.docker.com/desktop/install/windows-install/
Select Docker Desktop for Windows and wait for the installer file to download.
Open the downloaded installer file, and then follow the online instructions to install Docker Desktop.

The installation process takes about 5 minutes.
Once the installation has completed, select Close and restart.
When the updated virtual machine restarts, wait for the Docker Subscription Service Agreement window to appear.
On the Docker Subscription Service Agreement page, select Accept.
On the Finish setting up Docker Desktop page, select Finish.
On the User Account Control page, select Yes.
On the Welcome to Docker Desktop page, select Continue without signing in.
On the Tell us about the work you do page, select Skip.
Wait for the Docker Engine startup process to complete, and then minimize the Docker Desktop app.

Do not close Docker Desktop, just minimize the running app.

Task 4: Install the .NET 8 SDK

Complete the following steps to install the .NET 8 SDK.

Open a web browser window, and then navigate to the .NET 8 SDK download page: https://dotnet.microsoft.com/download
Select .NET SDK x64
Once the download is complete, open the installation file and follow the online instructions to install the .NET 8 SDK.
Close the browser window.

Task 5: Configure Visual Studio Code with C#, Docker, and Azure App Service extensions

Complete the following steps to configure Visual Studio Code with extensions.

Open a web browser window, and then navigate to the Visual Studio Code download page: https://code.visualstudio.com/download
Select Windows, and wait for the installer file to download.
Open the Visual Studio Code Installer file.
Accept the license agreement, and then continue to accept the default settings until you complete the installation.
Open Visual Studio Code.
On the Activity bar, select Extensions.

The Activity bar is the vertical menu on the left side of the Visual Studio Code user interface.
In the Search Extensions in Marketplace textbox, enter C#

Entering “C#” filters the list of extensions to show only the extensions that have something to do with C# coding.
In the filtered list of available extensions, select the extension labeled “C# Dev Kit - Official C# extension from Microsoft” that’s published by Microsoft.
To install the extension, select Install.
Wait for the installation to complete.

The C# Dev Kit takes about 1 minute to install.
On the EXTENSIONS view, replace C# with docker.
In the filtered list of available extensions, select the extension labeled Docker that’s published by Microsoft.
To install the extension, select Install.
On the EXTENSIONS view, replace docker with azure app service.
In the filtered list of available extensions, select the extension labeled Azure App Service that’s published by Microsoft.
To install the extension, select Install.
Close Visual Studio Code.

Exercise 3: Create and configure app deployment resources

In this exercise, you configure an Azure DevOps project and Azure Pipeline, create and push a Docker image to your Container Registry, and deploy a self-hosted Windows agent.

It will take about 40 minutes to complete the following tasks:

Configure an Azure DevOps project and initialize your code repository.
Create a .NET app and sync to your Azure DevOps repository.
Create a Docker image and push the image to your Azure Container Registry.
Create an Azure Pipeline named Pipeline1.
Deploy a self-hosted Windows agent.

Task 1: Configure Azure DevOps project and initialize code repository

Complete the following steps to configure Azure DevOps project.

Open a browser window, and then navigate to the Azure portal: https://portal.azure.com/
On the top search bar, in the Search textbox, enter devops
In the search results, select Azure DevOps organizations.
Select My Azure DevOps Organizations.
On the We need a few more details page, select Continue.
On the Get started with Azure DevOps page, select Create new organization, and then select Continue.
On the Almost done page, enter the displayed characters, and then select Continue.
On your Azure DevOps organization page, select Organization settings.
On the left side menu under Security, select Policies.
Set Allow public projects to On, and then select Save.
Navigate back to your DevOps organization page.
Under Create a project to get started, enter the following information:
- Project name: AZ2003Project
- Description: AZ2003 code project
- Visibility: Public
Select Create project.
On the left-side menu of your AZ2003Project page, select Repos.
Under Initialize main branch with a README or gitignore, select Initialize.
Select Clone, and then select Clone in VS Code.
On the This site is trying to open Visual Studio Code dialog, select Open.
On the Allow an extension to open this URI dialog, select Open.
In the choose a folder to clone window, select Desktop, select New Folder, type AZ2003 and then press Enter.
Select Select as Repository Destination.
On the Would you like to open the cloned repository dialog, select Open, and then select Yes, I trust the authors.

Task 2: Create a .NET app and sync to your Azure DevOps repository

Complete the following steps to create a .NET app and sync to your Azure DevOps repository.

On the Visual Studio Code Terminal menu, select New Terminal.
At the terminal command prompt, to verify that the .NET SDK has installed properly, enter the following command:
```
 dotnet --version
```
If you get an error telling you that the term “dotnet” is not recognized, complete the following:
- On the Windows Start menu, open Windows Settings.
- In Settings, open the Apps tab, and then select Installed Apps.
- Locate Microsoft .NET SDK 8.0.100 (x64) in the list of installed apps.
- To the right of Microsoft .NET SDK 8.0.100 (x64), select the ellipsis (…) and then select Modify.
- To allow the app to make changes, select Yes.
- On the Microsoft .NET SDK 8.0.100 window, select Repair.
- Wait for the repair operation to complete successfully, and then select Close.
- Close the Settings window.
- Switch back to the Visual Studio Code window, and then close Visual Studio Code.
- Re-open Visual Studio Code.
- In the Visual Studio Code Terminal, at the command prompt, enter dotnet --version
- You should see a version number displayed. For example: 8.0.100.
At the terminal command prompt, to configure the Git email setting, use the following command:

Enter git config –global user.email followed by the account email information provided in your lab environment

For example: git config –global user.email LabUser-12345678@labhoster.onmicrosoft.com
At the terminal command prompt, to configure Git username, use the following command:

Enter git config –global user.name followed by the account user name information provided in your lab environment

For example: git config –global user.name LabUser-12345678
On the View menu, select Command Palette.
At the command prompt, select .NET: New Project, and then select ASP.NET Core Empty.
Wait for resources to load, and then enter the following information:
- In the Name the new project text box, enter AZ2003App
- Accept the Default directory.
Open the terminal command prompt, and then run the following dotnet CLI command:
```
 dotnet build
```
In the root project folder, create a .gitignore file that contains the following information:
```
 [Bb]in/
 [Oo]bj/
```
On the File menu, select Save All.
Open the Source Control view.
In the commit message text box, enter initial commit.
Select Commit, and then select Yes to stage and commit changes.
Select Sync Changes, and then select OK to sync your files to the DevOps repo.
On the Git Credential Manager dialog, enter your lab environment credentials (Username and Password).

Task 3: Create a Docker image and push the image to your Azure Container Registry

Complete the following steps to create a Docker image and push the image to your Azure Container Registry.

Ensure that you have your AZ2003 code project open in Visual Studio Code.
To create a Dockerfile, run the following command from the Command Palette: Docker: Add Docker Files to Workspace.
When prompted, specify the following information:
- Application Platform: .NET ASP.NET Core.
- Operating System: Linux.
- Ports: 5000.
- Include Docker Compose Files: No
To create a Docker image, run the following command in the Command Palette: Docker Images: Build Image.
Wait for the image build process to complete, and then close the Terminal.
On the left side menu, to open the Docker view, select Docker.
In the DOCKER view, under Registries, select Connect Registry, and then select Azure Azure Container Registry.
In the DOCKER view, expand Azure, and then select Allow.
In the browser window, select the Azure account that you’re using for this lab.
Return to Visual Studio Code.
In the DOCKER view, expand the Azure subscription, and verify that the Azure Container Registry that you created is listed.
To push the Docker image to the Azure Container Registry, run the following command in the Command Palette: Docker Images: Push.
When the command runs, complete the following steps:
- Select image group: select az2003project
- Select image (tag): select latest
- Select registry provider: select Azure
- Select your subscription.
- Select an Azure Container Registry to push to: select the container registry that you created. For example: acraz2003cah12oct.
- To deploy the image, press Enter.
Wait for the image push process to complete, and then close the Terminal.
Open the Source Control view, enter a commit message, and then Commit and Sync Changes.

Task 4: Create an Azure Pipeline named Pipeline1

Complete the following steps to create an Azure Pipeline named Pipeline1.

Open the Azure DevOps project.
On the left-side menu, select Pipelines.
Select Create Pipeline.
Select Azure Repos Git.
On the Select a repository page, select AZ2003Project.
Select Starter pipeline.
Under Save and Run, select Save, and then select Save.
To change the name of your pipeline to “Pipeline1”, complete the following steps:
1. On the left-side menu, select Pipelines.
2. To the right of the AZ2003Project pipeline, select More options, and then select Rename/move.
3. In the Rename/move pipeline dialog, under Name, enter Pipeline1 and then select Save.

Task 5: Deploy a self-hosted Windows agent

For an Azure Pipeline to build and deploy Windows, Azure, and other Visual Studio solutions you need at least one Windows agent in the host environment.

Complete the following steps to deploy a self-hosted Windows agent.

Navigate to the home page of your DevOps organization.
In the upper right corner, select User settings.
On the User settings dialog, select Personal access tokens.
To create a personal access token, select + New Token.
Under Name, enter AZ2003.
At the bottom of the Create a new personal access token window, to see the complete list of scopes, select Show all scopes.
For the scope, select Agent Pools (read, manage) and Deployment group (read, manage).

Ensure that all the other boxes are cleared.
Select Create.
On the Success page, to copy the token, select Copy to clipboard and then select Close.
Open Notepad, and then save a copy of the token to Notepad.

You will use this token when you configure the agent.
Navigate to your DevOps organization, and then select Organization settings.
On the left side menu under Pipelines, select Agent pools.
If the Get the agent dialog box opens, skip to the next step, otherwise complete the following steps:
1. To select the default pool, select Default.
  
  If the default pool doesn’t exist, select Add pool, and then enter the following information:
  1. Under Pool type, select Self-hosted.
  2. Under Name, enter Default
  3. Select Create.
  4. To open the pool that you just created, select Default.
2. Under Default, select the Agents tab, and then select New agent.
On the Get the agent dialog box, complete the following steps:
1. Select the Windows tab.
2. On the left side pane, select x64.
3. On the right side pane, select Download.
Wait for the download to complete.
Close the Get the agent dialog.

The next series of instruction steps walk you through the “Create the agent” process.
Use Windows File Explorer to create the following folder location for the agent:
```
 C:\agents
```
Use Windows File Explorer to unpack the downloaded agent zip file into the agents directory that you just created.
Wait for the file extraction process to complete, and then close File Explorer.
Open Windows PowerShell as an Administrator, navigate to the agents directory, and then enter the following PowerShell command:
```
 .\config
```
Respond to the configuration prompts as follows:
- Enter server URL >: enter the URL for your DevOps organization. Such as: https://dev.azure.com/<your organization>
- Enter authentication type (press enter for PAT) >: press Enter.
- Enter personal access token >: Paste-in the personal access token that you copied to Notepad.
- Enter agent pool (press enter for default) >: press Enter.
- Enter agent name (press enter for YOUR-PC-NAME) > enter az2003-agent
- Enter work folder (press enter for _work) >: press Enter.
- Enter run agent as service? (Y/N) (press enter for N) >: enter Y
- Enter enable SERVICE_SID_TYPE_UNRESTRICTED for agent service (Y/N) (press enter for N) >: enter Y
- Enter User account to use for the service (press enter for NT AUTHORITY\NETWORK SERVICE) >: press Enter.
- Enter whether to prevent service starting immediately after configuration is finished? (Y/N) (press enter for N) >: press Enter.
A message informing you that the agent started successfully is displayed.

For extra help, see the following documentation: https://learn.microsoft.com/azure/devops/pipelines/agents/windows-agent
Close Windows PowerShell.

Exercise 4: Configure Azure Container Registry for a secure connection with Azure Container Apps

You’ve been asked to configure Azure resources that meet the following requirements:

Your resource group must include a user-assigned managed identity.
Your container registry must be able to use the managed identity to pull artifacts.
Access for the managed identity must be limited using the principle of least privilege.
Your container registry must be accessible from a private endpoint on VNET1/PESubnet.

In this exercise, you’ll configure a container registry instance for a secure connection with a container app.

It will take about 10 minutes to complete the following tasks:

Configure a user-assigned managed identity.
Configure your container registry with AcrPull permissions for the managed identity.
Configure your container registry with a private endpoint connection.

Task 1: Configure a user-assigned managed identity

Complete the following steps to configure a user-assigned managed identity.

Open your Azure portal.
In the top search bar of the Azure portal, enter managed identity
In the filtered list of resources, select User Assigned Managed Identity.
On the Create User Assigned Managed Identity page, specify the following information:
- Subscription: Specify the Azure subscription that you’re using for this guided project.
- Resource group: RG1
- Region: Enter the Region that matches the region setting of your resource group.
- Name: uai-az2003
Select Review + create.
Wait while settings are validated, and then select Create.
Close the managed identity page.

Task 2: Configure your container registry with AcrPull permissions for the managed identity

Complete the following steps to configure Container Registry with AcrPull permissions for the managed identity.

In the Azure portal, open your Container Registry resource.
On the left-side menu, select Access Control (IAM).
On the Access Control (IAM) page, select Add role assignment.
Search for the AcrPull role, and then select AcrPull.
Select Next.
On the Members tab, to the right of Assign access to, select Managed identity.
Select + Select members.
On the Select managed identities page, under Managed identity, select User-assigned managed identity, and then select the user-assigned managed identity created for this project.

For example: uai-az2003.
On the Select managed identities page, select Select.
On the Members tab of the Add role assignment page, select Review + assign.
On the Review + assign tab, select Review + assign.
Wait for the role assignment to be added.

A notification will appear, but if you miss it, you can check the Role assignments tab to verify that uai-az2003 has been assigned the AcrPull role.

Task 3: Configure your container registry with a private endpoint connection

Complete the following steps to configure your container registry with a private endpoint connection.

Ensure that your Container Registry resource is open in the portal.
Under Settings, select Networking.
On the Private access tab, select + Create a private endpoint connection.
On the Basics tab, under Project details, specify the following information:
- Subscription: Specify the Azure subscription that you’re using for this guided project.
- Resource group: RG1
- Name: pe-acr-az2003
- Region: Ensure that specified Region matches the region setting of your resource group.
Select Next: Resource.
On the Resource tab, ensure the following information is displayed:
- Subscription: Ensure that the Azure subscription that you’re using for this guided project is selected.
- Resource type: Ensure that Microsoft.ContainerRegistry/registries is selected.
- Resource: Ensure that the name of your registry is selected.
- Target sub-resource: Ensure that registry is selected.
Select Next: Virtual Network.
On the Virtual Network tab, under Networking, ensure the following information is displayed:
- Virtual network: Ensure that VNET1 is selected
- Subnet: Ensure that PESubnet is selected.
Select Next: DNS.
On the DNS tab, under Private DNS Integration, ensure the following information is displayed:
- Integrate with private DNS zone: Ensure that Yes is selected.
- Private DNS Zone: Notice that (new) privatelink.azurecr.io is specified.
Select Next: Tags.
Select Next: Review + create.
On the Review + create tab, when you see the Validation passed message, select Create.
Wait for the deployment to complete.
When you see Your deployment is complete displayed, close the private endpoint deployment page.

Exercise 5: Create and configure a container app in Azure Container Apps

You’ve been asked to configure a Container App that meets the following requirements:

Is deployed to VNET1/ACASubnet.
Pulls an image from a container registry.
Authenticates using a user-assigned managed identity (uai-az2003).
Uses Container App to connect to a Service Bus instance using the .NET client type.
The app can run up to two replicas that are added whenever there are 1000 concurrent HTTP requests.

In this exercise, you’ll deploy a container app from an image in the Azure Container Registry to the Azure Container Apps platform.

It will take about 20-25 minutes to complete the following tasks:

Create a Container App that uses an Azure Container Registry image.
Configure the container app to authenticate using the user assigned identity.
Configure a connection between the container app and Service Bus.
Configure HTTP scale rules.

Task 1: Create a Container App that uses an Azure Container Registry image

Complete the following steps to create a Container App that uses an Azure Container Registry image.

In the top search bar of the Azure portal, enter container app
In the filtered list of resources, select Container Apps.
On the Container Apps page, select Create container app.
On the Basics tab, specify the following:
- Subscription: Specify the Azure subscription that you’re using for this guided project.
- Resource group: RG1
- Container app name: aca-az2003
- Region: Ensure that specified Region matches the region setting of VNET1 (which should match your resource group location).
  
  The container app needs to be in the same region/location as the virtual network so you can choose VNET1 for the managed environment. For this guided project, keep all of your resources in the region/location specified for your resource group.
- Container Apps Environment: Select Create new.
On the Create Container Apps Environment page, select the Networking tab, and then specify the following:
- Use your own virtual network: Select Yes.
- Virtual network: Select VNET1.
- Infrastructure subnet: ACASubnet.
[!NOTE] If the ACASubnet subnet is not listed, cancel this create process, open your virtual network resource, adjust the ACASubnet address range to 10.0.2.0/23, and then restart the steps to create the Container App resource.
On the Create Container Apps Environment page, select Create.
On the Create Container App page, select the Container tab, and then specify the following:
- Use quickstart image: Uncheck this setting.
- Name: Ensure that aca-az2003 is specified.
- Image source: Ensure that Azure Container Registry is selected.
- Registry: Select your container registry. For example: acraz2003cah12oct.azurecr.io
- Image: Select az2003project
- Image tag: Select latest
Select Review + create.
Once verification has Passed, select Create.
Wait for the deployment to complete.

[!NOTE] This deployment can take 5-10 minutes to complete.

Task 2: Configure the container app to authenticate using the user assigned identity

Complete the following steps to configure the container app to authenticate using the user assigned identity.

On the Azure portal, open the Container App that you created.
Under Settings, select Identity.
Select the tab for User assigned.
Select Add user assigned managed identity.
On the Add user assigned managed identity page, select uai-az2003, and then select Add.

Task 3: Configure a connection between the container app and Service Bus

Complete the following steps to configure a connection between the container app and Service Bus.

On the Azure portal, ensure that you have your Container App open.
Under Settings, select Service Connector (Preview).
Select Connect to your Services.
On the Create connection page, specify the following:
- Service type: Select Services Bus.
- Client type: Select .NET.
Select Next: Authentication.
On the Authentication tab, select User assigned managed identity.
To change tabs, select Review + Create.
Once the Validation passed message appears, select Create.
Wait for the connection to be created.

The Service Bus connection will be listed on the Service Connector (preview) page.

Task 4: Configure HTTP scale rules

Complete the following steps to configure HTTP scale rules for your Container App.

Ensure that your Container App is open in the portal.
On the left-side menu under Application, select Revisions and replicas.
Notice the Name assigned to your active revision.
On the left-side menu under Application, select Scale.
At the top of the page, select Edit and deploy.
At the bottom of the page, select Next : Scale.
Configure the Min / max replicas as follows:
- Set Min replicas: 0
- Set Max replicas: 2
Under Scale rule, select + Add.
On the Add scale rule page, specify the following:
- Rule name: Enter scalerule-http
- Type: Select HTTP scaling.
- Concurrent requests: Set the value to 1000.
On the Add scale rule page, select Add.
On the Create and deploy new revision page, select Create.
Ensure that your new scale rule is displayed.

If the scale rule is not displayed after refreshing, check the Revisions tab to see the current active revision, and then adjust the selected Revision on the Scale and replicas page if needed.

Exercise 6: Configure continuous integration by using Azure Pipelines

You’ve been asked to configure a continuous integration environment for Container Apps that meets the following requirements:

You need an Azure Container Apps deployment task in your ADO environment.
Pipeline1 must deploy a container image from your container registry to your container app using a self-hosted agent pool.
You must ensure that the pipeline successfully deploys the image at least once.

In this exercise, you deploy a container app from an image in the Azure Container Registry to the Azure Container Apps platform.

It will take about 10 minutes to complete the following tasks:

Configure Pipeline1 to use the self-hosted agent pool.
Configure Pipeline1 with an Azure Container Apps deployment task.
Run the Pipeline1 deployment task.

Task 1: Configure Pipeline1 to use the self-hosted agent pool

Complete the following steps to configure your pipelines to use the self-hosted agent pool.

Ensure that you have your Azure DevOps organization open on its own browser tab.

If needed, open a new browser tab, navigate to https://dev.azure.com, and then open your Azure DevOps organization.
On your Azure DevOps page, to open your DevOps project, select AZ2003Project.
In the left-side menu, select Pipelines.
Select Pipeline1, and then select Edit.
To use the self-hosted agent pool, update the azure-pipelines.yml file as shown in the following example:
```
 trigger:
 - main

 pool:
   name: default

 steps:
```
Select Save.
Enter a commit message, and then select Save.

Task 2: Configure Pipeline1 with an Azure Container Apps deployment task

Complete the following steps to configure Pipeline1 with an Azure Container Apps deployment task.

Ensure that you have Pipeline1 open for editing.
On the right side under Tasks, in the Search tasks field, enter azure container
In the filtered list of tasks, select Azure Container Apps Deploy
Under Azure Resource Manager connection, select the Subscription you’re using, and then select Authorize.
In the Azure portal tab, open your Container App resource, and then open the Containers page.
Copy the following information to Notepad.
- Name
- Registry
- Image
- Image tag
Use the information that you copied from the Containers page to configure the following Task information fields:
- Docker Image to Deploy: Registry/Image:Image tag (replace with your information from Notepad)
- Azure Container App name: Name (replace with your information from Notepad)
For example:
- Docker Image to Deploy: acraz2003cah12oct.azurecr.io/az2003project:latest
- Azure Container App name: aca-az2003
In the Azure Resource group name field, enter RG1

[!NOTE] If you need to verify the resource group name, you can find it on the Overview page of your Container App resource.

On the Azure Container Apps Deploy page, select Add.

The Yaml file for your pipeline should now include the AzureContainerApps tasks as follows:

 trigger:
 - main
 pool:
   name: default
 steps:
 - task: AzureContainerApps@1
   inputs:
     azureSubscription: '<Subscription>(<Subscription ID>)'
     imageToDeploy: '<Registry>/<Image>:<Image tag>' from Container App resource
     containerAppName: '<Name>' from Container App resource 
     resourceGroup: '<resource group name>'

Here’s an example that shows a YAML configuration snippet:

 trigger:
 - main
 pool:
   name: default
 steps:
 - task: AzureContainerApps@1
   inputs:
     azureSubscription: 'Visual Studio Enterprise(1111aaaa-22bb-33cc-44dd-555555eeeeee)'
     imageToDeploy: 'acraz2003cah12oct.azurecr.io/aspnetcorecontainer:latest'
     containerAppName: 'aca-az2003'
     resourceGroup: 'RG1'

On your Pipeline1 page, select Save, enter a commit message, and then select Save again to commit.

Task 3: Run the Pipeline1 deployment task

Complete the following steps to run the Pipeline1 deployment task.

Ensure that you have Pipeline1 open in Azure DevOps.
To run the AzureContainerApps task, select Run.
On the Run pipeline page, select Run.

A pipeline page opens to display the associated job. The job section displays job status, which progresses from Queued to Waiting.
Check to see if ‘Permission needed’ is displayed under Job.

If the job requires permission to proceed, select View, and then select Permit to provide the required permissions.
Monitor the status of the run operation and verify that the run is successful.

It can take a few minutes for queued job to start running. After a minute or so, the job status should change from “Running” to “Success”.

Exercise 7: Manage revisions in Azure Container Apps

You’ve been asked to configure traffic splitting for your Container Apps to meet the following requirements:

You need to create a new revision of the container app that uses a suffix of v2.
You must ensure that 25 percent of requests to your app are directed to the v2 revision.
You must label the revisions “current” and “updated” and ensure that requests to the “—updated” revision are directed to the revision labeled v2.

In this exercise, you deploy a new revision of your container app and configure traffic splitting between two labeled revisions.

It will take about 5-10 minutes to complete the following tasks:

Set revision management to multiple.
Create a new revision with a v2 suffix.
Configure labels on the revisions.
Configure a traffic percentage on the revisions.

Task 1: Set revision management to multiple

Complete the following steps to set revision management to multiple.

In the Azure portal, open your container app resource.
On the left side menu, under Application, select Revisions and replicas.
At the top of the Revisions page, select Choose revision mode.
To switch from single to multi-revision mode, select Confirm.
On the Revisions page, wait for the Revision Mode setting to update.

The Revision Mode will be set to Multiple after the update is complete.

Task 2: Create a new revision with a v2 suffix

Complete the following steps to create a new revision with a v2 suffix.

In the Azure portal, ensure that you have the Revisions page of your container app resource open.
At the top of the page, select + Create new revision.
On the Create and deploy new revision page, complete the following steps:
- Name / suffix: Enter v2
- Under Container image, select your container image. For example, aca-az2003.
Select Create.
Wait for the deployment to be completed.

Task 3: Configure labels on the revisions

Ingress must be enabled before you can configure revision labels or traffic splitting.

Complete the following steps to configure labels on the revisions.

On the left-side menu, under Settings, select Ingress.
If Ingress isn’t enabled, select Enabled.
On the Ingress page, specify the following information:
- Ingress traffic: select Accepting traffic from anywhere.
- Ingress type: select HTTP.
- Client certificate mode: ensure that Ignore is selected.
- Transport: ensure that Auto is selected.
- Insecure connections: ensure that Allowed is NOT checked.
- Target port: enter 5000
- IP Security Restrictions Mode: ensure that Allow all traffic is selected.
At the bottom of the Ingress page, select Save, and then wait for the update to complete.
On the left-side menu, under Revisions, select Revisions and replicas.
For the v2 revision, under Label, enter updated
For the other revision, enter current
At the top of the page, select Save.
Wait for the Ingress setting to update.

Task 4: Configure a traffic percentage on the revisions

Complete the following steps to configure a traffic percentage on the revisions.

Ensure that you have the Revisions page open.
For the v2 revision, under Traffic, enter 25 as the percentage.
For the other revision, under Traffic, enter 75 as the percentage.
At the top of the page, select Save.