Tutorial: Create an Azure Container App on Azure Arc-enabled Kubernetes (Preview)

  • Article

In this tutorial, you create a Container app to an Azure Arc-enabled Kubernetes cluster (Preview) and learn to:

  • Create a container app on Azure Arc
  • View your application's diagnostics

Prerequisites

Before you proceed to create a container app, you first need to set up an Azure Arc-enabled Kubernetes cluster to run Azure Container Apps.

Add Azure CLI extensions

Launch the Bash environment in Azure Cloud Shell.

Launch Cloud Shell in a new window.

Next, add the required Azure CLI extensions.

Warning

The following command installs a custom Container Apps extension that can't be used with the public cloud service. You need to uninstall the extension if you switch back to the Azure public cloud.

az extension add --upgrade --yes --name customlocation
az extension add --name containerapp  --upgrade --yes

Create a resource group

Create a resource group for the services created in this tutorial.

myResourceGroup="my-container-apps-resource-group"
az group create --name $myResourceGroup --location eastus

Get custom location information

Get the following location group, name, and ID from your cluster administrator. See Create a custom location for details.

customLocationGroup="<RESOURCE_GROUP_CONTAINING_CUSTOM_LOCATION>"

customLocationName="<NAME_OF_CUSTOM_LOCATION>"

Get the custom location ID.

customLocationId=$(az customlocation show \
    --resource-group $customLocationGroup \
    --name $customLocationName \
    --query id \
    --output tsv)

Retrieve connected environment ID

Now that you have the custom location ID, you can query for the connected environment.

A connected environment is largely the same as a standard Container Apps environment, but network restrictions are controlled by the underlying Arc-enabled Kubernetes cluster.

myContainerApp="my-container-app"
myConnectedEnvironment=$(az containerapp connected-env list --custom-location $customLocationId -o tsv --query '[].id')

Create an app

The following example creates a Node.js app.

 az containerapp create \
    --resource-group $myResourceGroup \
    --name $myContainerApp \
    --environment $myConnectedEnvironment \
    --environment-type connected \
    --image mcr.microsoft.com/k8se/quickstart:latest \
    --target-port 80 \
    --ingress external

az containerapp browse --resource-group $myResourceGroup --name $myContainerApp

Get diagnostic logs using Log Analytics

Note

A Log Analytics configuration is required as you install the Container Apps extension to view diagnostic information. If you installed the extension without Log Analytics, skip this step.

Navigate to the Log Analytics workspace that's configured with your Container Apps extension, then select Logs in the left navigation.

Run the following sample query to show logs over the past 72 hours.

If there's an error when running a query, try again in 10-15 minutes. There may be a delay for Log Analytics to start receiving logs from your application.

let StartTime = ago(72h);
let EndTime = now();
ContainerAppConsoleLogs_CL
| where TimeGenerated between (StartTime .. EndTime)
| where ContainerAppName_s =~ "my-container-app"

The application logs for all the apps hosted in your Kubernetes cluster are logged to the Log Analytics workspace in the custom log table named ContainerAppConsoleLogs_CL.

  • Log_s contains application logs for a given Container Apps extension
  • AppName_s contains the Container App app name. In addition to logs you write via your application code, the Log_s column also contains logs on container startup and shutdown.

You can learn more about log queries in getting started with Kusto.

Next steps