09-update-application.md

Update and Deploy New Version of Application

In this lab, we will make a change to the web application and then re-deploy the new container image into AKS.

Perform these steps in the Jumpbox

Update web application code

1. Start with a terminal on the CentOS jumpbox via SSH

2. Logon to your Azure Subscription

   az login

3. Select the correct subscription

   az account list --output table
   az account set --subscription <subscriptionid>

4. Connect to you AKS cluster

   az aks list --output table
   az aks get-credentials --name <youraks> --resource-group <yourresourcegroup>

5. Navigate to ~/container-bootcamp/app/web/src/components/

6. Edit code for the Footer.vue

7. Find the snippet below (line 17) and change the text "Azure Global Blackbelt Team" to your name or whatever you would like to display.

   <div class="row at-row flex-center flex-middle">
     <div class="col-lg-6">
     </div>
     <div class="col-lg-12 credits">
       Azure Global Blackbelt Team
     </div>
     <div class="col-lg-6">
     </div>
   </div>

8. Save your edits and close the file

Create new container image and push to ACR

1. Browse to ~/container-bootcamp/app/web

2. You should still have a Dockerfile created in an earlier lab

3. Create a new image with an updated image tag

   docker build -t rating-web:new-version .

4. Tag the new image and push to your Azure Container Registry.

   # you may need to login again to your ACR. set these values to yours
   ACR_SERVER=<acr_server>
   ACR_USER=<acr_user>
   ACR_PWD=<acr_pass>
   
   docker login --username $ACR_USER --password $ACR_PWD $ACR_SERVER
   
   docker tag rating-web:new-version $ACR_SERVER/azureworkshop/rating-web:new-version
   
   docker push $ACR_SERVER/azureworkshop/rating-web:new-version

5. Verify that the new version of the image was pushed to ACR by checking your registry in the Azure Portal

Update kubernetes deployment

There are two ways to update the application with the new version. Both are described below. Choose one to proceed.

1. Edit the YAML file and re-apply
2. Update the deployment and re-set the image tag

Option 1: Edit YAML and apply

1. As we did in a prior lab, open the helper-files directory and review the file heroes-web-api.yaml

2. Update the yaml file and replace the tag from v1 to new-version for heroes-web

    template:
   metadata:
     labels:
       name:  heroes-web
   spec:
   containers:
   - image: mycontainerregistry.azurecr.io/azureworkshop/rating-web:new-version
       name:  heroes-web-cntnr

3. Apply the new yaml file

   cd ~/container-bootcamp/labs/helper-files
   
   kubectl apply -f heroes-web-api.yaml

Option 2: Update the deployment

1. Set the new image tag on the deployment object

   kubectl get deploy

   NAME                DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
   heroes-api-deploy   1         1         1            1           29m
   heroes-db-deploy    1         1         1            1           32m
   heroes-web-depoy    1         1         1            1           29m

   kubectl set image deployment/heroes-web-deploy heroes-web-cntnr=$ACR_SERVER/azureworkshop/rating-web:new-version

Check status

1. You can see the updates and history for the changes from above. The following command will verify that latest deployment was successful.

   kubectl rollout status deployment/heroes-web-deploy

   Each deployment will create a new replicaset:

   kubectl get replicaset | grep web

   heroes-web-556f6f976c          0         0         0         34m
   heroes-web-64f4795689          0         0         0         8m
   heroes-web-67b4b7b887          1         1         1         1m

   kubectl rollout history deployment/heroes-web-deploy

Browse to your newly deployed web application

Browse to the web application on the Public IP and validate that the change you made to the 'Footer.vue' file is reflecting in the portal.

Return back to BootCamp Table of Contents (Main Page)