Lab: Build Application Components and Prerequisites

In this lab we will build Docker containers for each of the application components and setup the back-end database.

Prerequisites

• Complete previous labs:
  • Azure Kubernetes Service

NOTE: If you restarted your shell session, you need to reload your environment variables. You can use the following command: source ~/workshopvars.env

Instructions

1. Create Azure Container Registry (ACR)
   • Use the same resource group that was created for AKS (in lab 1)
   • In this step, you will need a unique name for your ACR instance. Use the following step to create the ACR name and then deploy.

    # Use the UNIQUE_SUFFIX from the first lab. Validate that the value is still set.
    echo $UNIQUE_SUFFIX
    # Set Azure Container Registry Name
    export ACRNAME=acrhackfest$UNIQUE_SUFFIX
    # Check ACR Name (Can Only Container lowercase)
    echo $ACRNAME
    # Persist for Later Sessions in Case of Timeout
    echo export ACRNAME=acrhackfest$UNIQUE_SUFFIX >> ~/workshopvars.env
    # Create Azure Container Registry
    az acr create --resource-group $RGNAME --name $ACRNAME --sku Basic
   

2. Attach the Azure Container Registery to the AKS Cluster

    az aks update -n $CLUSTERNAME -g $RGNAME --attach-acr $ACRNAME
   

   NOTE: If the role assignment fails due to permissions, we will do it the hard way and create an Image Pull Secret.

    # !!!!!!!!!!
    # Only do these steps if the above Service Principal Role Assignment fails.
    # !!!!!!!!!!
   
    # Extract Container Registry details needed for Login
    # Login Server
    ACR_FQDN=$(az acr show -n $ACRNAME --query "{acrLoginServer:loginServer}" -o tsv)
    # Enable ACR admin 
    az acr update -n $ACRNAME --admin-enabled true
    # Registry Username and Password
    ACR_USER=$(az acr credential show -n $ACRNAME --query "username" -o tsv)
    ACR_PASSWD=$(az acr credential show -n $ACRNAME --query "passwords[0].value" -o tsv)
   
    # Use the login and credential information from above
    kubectl create -n hackfest secret docker-registry regcred \
      --docker-server=$ACR_FQDN \
      --docker-username=$ACR_USER \
      --docker-password=$ACR_PASSWD
   
    # !!!!!!!!!!
    # Only do these steps if the above Service Principal Role Assignment fails.
    # !!!!!!!!!!
   

3. Create Application Insights Instance

   Continue using the same resource group that was created previously

    # Create a unique application insights name
    APPINSIGHTSNAME=appInsightshackfest$UNIQUE_SUFFIX
    # Deploy the appinsights ARM template   
    az deployment group create --resource-group $RGNAME --template-file labs/build-application/app-Insights.json --parameters type=Node.js name=$APPINSIGHTSNAME regionId=eastus
   

    # Get the Instrumentation Key. If you get an error, wait a few seconds and run this again.
    export APPINSIGHTS_INSTRUMENTATIONKEY=$(az resource show -g $RGNAME -n $APPINSIGHTSNAME --resource-type "microsoft.insights/components" --query properties.InstrumentationKey -o tsv)
   

4. Create Kubernetes secrets for access to App Insights

   You will use a secret to hold the API Key for App Insights. This is used by the pods once we deploy the app.

    kubectl create secret generic app-insights-secret --from-literal=appinsights=$APPINSIGHTS_INSTRUMENTATIONKEY -n hackfest
   

5. Create Docker containers in ACR

   In this step we will create a Docker container image for each of our microservices. We will use ACR Builder functionality to build and store these images in the cloud.

    az acr build -t hackfest/data-api:1.0 -r $ACRNAME --no-logs -o json app/data-api --no-wait
    az acr build -t hackfest/flights-api:1.0 -r $ACRNAME --no-logs -o json app/flights-api --no-wait
    az acr build -t hackfest/quakes-api:1.0 -r $ACRNAME --no-logs -o json app/quakes-api --no-wait
    az acr build -t hackfest/weather-api:1.0 -r $ACRNAME --no-logs -o json app/weather-api --no-wait
    az acr build -t hackfest/service-tracker-ui:1.0 -r $ACRNAME --no-logs -o json app/service-tracker-ui --no-wait
   

   You can see the status of the builds by running the command below.

    az acr task list-runs -r $ACRNAME -o table
   
    az acr task logs -r $ACRNAME --run-id <run id>
   

   Browse to your ACR instance in the Azure portal and validate that the images are in “Repositories.”

Troubleshooting / Debugging

• Make sure all of you ACR Task commands are pointing to the correct Azure Container Registry. You can check repositories by navigating to your ACR in the Azure Portal UI.

Docs / References

• Azure Container Registry Docs. https://docs.microsoft.com/en-us/azure/container-registry

Next Lab: Helm Setup and Deploy Application