Skip to content

Latest commit

 

History

History
152 lines (108 loc) · 7.83 KB

solution5.md

File metadata and controls

152 lines (108 loc) · 7.83 KB
Raw

Challenge 5: The Solution

This page will take you step by step through solving challenge five.

Solution Steps:

From your Visual Studio Server, deploy the eShoponWeb application to AKS

  • Install Docker Desktop and restart your Visual Studio VM.
  • This step is required before you can add Docker support to your eShoponWeb app in Visual Studio.

  • Click the link

  • Follow the instructions to complete the WSL 2 installation and restart Docker Desktop

  • Navigate to c:\eshoponweb\eShopOnWeb-master

  • Double-click on eShopOnWeb.sln solution file and select Visual Studio 2019 when prompted.
  • Sign into Visual Studio if you have not already done so.
  • Once Visual Studio opens and settles down.
  • Update your DB connection strings in appsettings.json to use the SQL server IP address instead of hostname.

Tip: You can get the SQL private IP from the VM in Azure Portal.

  • Right-click on Web the Add then Add Docker Support.

  • Leave the default option of Linux selected and click OK.
  • Regenerate a new Dockerfile and wait for task to complete.
  • When prompted click Allow access to your docker back-end to communicate with Private Networks.


When Docker support has been added, you should see a Docker option to run/debug your app.

  • Click to run your app. Wait a few minutes for your app to build and load.
  • When its complete Visual Studio will open the URL in the default browser.
  • Your app is now running in a local container, click Stop or close the Browser.

From Azure Monitor, locate the container running the eShoponWeb application

Now, let's move on to publishing the app to AKS.

  • Go to the Azure Portal and create an Azure Container registry with a Standard SKU in your workshop resource group.

  • Once your Container Registry is created, return to Visual Studio and right click on Web to publish.

  • Choose Azure, Azure Container Registry as your Publish target and select the Container Registry that you just created.
  • Click Finish.

  • Next, navigate to the Connected Services for Web.
  • Configure Application Insights to be Azure Application Insights
  • Your App Insights resource and Save connection string value in None
  • Configure SQL DB CatalogConnection to point to SQL Server Database
  • Update connection string(s) using the Catalog string found in appsettings.json and Save connection string in None.
  • Configure SQL DB IdentityConnection to point to SQL Server Database
  • update connection string using the Identity string found in appsettings.json and Save connection value string in None
  • Update Secrets.json(Local)

  • Return to Publish and click on Publish to push your app up to the Container Registry. This step will take several minutes. The final Visual Studio output should indicate successful push.

  • Open the provided deployment.yml file in sources\aks and update the image name to point to your Container Registry Login server and image.

  • Update the server name as shown below

  • Upload the LogReaderRBAC.yml, deployment.yml and service.yml files to your cloud shell or browse to the sources/aks folder
  • Run the following commands:
az aks get-credentials --resource-group YOUR_RESOURCE_GROUP --name YOUR_AKS_NAME

Tip: If you don't have kubectl installed run the command below: az aks install-cli

  • Check connectivity to and the state of your AKS nodes, run: kubectl get nodes


You may not see all nodes, as this is also hosted on a VMSS.

Important: You will need to give access to your AKS cluster on the Container Registry (ACR) to be able to pull the image and deploy it. To do so and for learning purposes give both the AKS and the Agent Pool Contributor rights on the ACR. The AKS and the Agentpool Manage Identities are called after the AKS name.

  • Run the following command to deploy the cluster role bindings: kubectl create -f LogReaderRBAC.yml

  • Run the following command to deploy your app kubectl apply -f deployment.yml

  • Run the folowing command after few mints to check the status of the pods: kubectl get pods

  • Run the following command to expose your app front-end on port 8080 kubectl apply -f service.yml

  • After a few minutes, check on the status of your service kubectl get services

  • Use the external IP of the web-service and port 8080 to access your app deployed on AKS.

  • Return to the Azure Portal.
  • Navigate to Azure Monitor, click on Containers, and select your cluster.

  • Alternatively you can go to your AKS, and click Insights
  • Click on Containers and then search for web

  • Or go to Controllers and search for web

  • Generate an exception in the eShoponWeb application

Tip: Try to change your password, similar to the exception generated in the Application Insights challenge

  • Login
  • Enter the user and password provided on the page.
  • Click on My account

  • Click on Password Notice an exception is thrown

  • Click on the Web container and View container live data.

  • Trip the password exception again once the Status has gone from Unk to Ok.
    You can search for Rob, should find it in the logs!

First person to post a screenshot of the live log with the exception message wins the challenge :-)