1.1 Dockerfile in folder web

If you open folder web, you’ll see that the Dockerfile is empty.

Time to make sure that we can build an image from this Dockerfile and we can run a container from that image.

1.2 The environment variables

When testing the image of the service web, you may have noticed that we passed the file tripmeal.env as an argument to the command docker run. This file contains the definition of environment variables that are used in the application. Open this file and look at the environment variables to answer the following questions.

1.3 Volumes and networks

The TripMeal application keeps user information and recipe information in a database. Therefore, you’ll need to define a Docker volume to hold the data.

The containers composing the TripMeal application need to communicate through a Docker network.

1.4 The compose file

You’re finally ready to complete the file docker-compose.yml.

If you successfully deployed the application, you can continue.

3.1 Login to Azure through CLI

Whether you’re on Windows, macOS or Linux, you need to open a terminal.

In order to log in to your Azure account, type the following command:

az login

A Web page will open in your default Web browser, where you can type your username and password (your CentraleSupélec credentials). After authenticating your Azure account, you can go back to the terminal, where you should see some information about your account, such as:

[
  {
    "cloudName": "AzureCloud",
    "homeTenantId": "<id>",
    "id": "<id>",
    "isDefault": true,
    "managedByTenants": [],
    "name": "Azure for Students",
    "state": "Enabled",
    "tenantId": "<id>",
    "user": {
      "name": "<email-address>",
      "type": "user"
    }
  }
]

3.2 Deploy and use Azure Container Registry

When we run TripMeal on a local Kubernetes cluster, we assumed that our computer could have a direct access to the Internet and, therefore, to the DockerHub registry, where we could pull the images of the TripMeal services. When we run a containerized application in production, we cannot make this assumption as the production servers have often no direct access to the Internet.

We need to place the images in a container registry that is in the same context as our production servers. Since we’re going to run the application on Azure, we can use the Azure Container Registry (ACR).

3.3 Deploy a Kubernetes cluster

We now deploy a Kubernetes cluster on Azure.

az aks create \
    --resource-group RES_GRP_NAME \
    --name CLUSTER_NAME \
    --node-count 2 \
    --generate-ssh-keys \
    --attach-acr REG_NAME

3.4 Deploy the application

We’re almost done! The images are in the registry, the Kubernetes cluster is up and running. The only missing piece of the puzzle is our application TripMeal.

First thing to do is to slightly modify the file tripmeal.yml that you created at the end of the previous section.

It is the moment you’ve been waiting for! Deploy your application by typing the following command:

kubectl apply -f tripmeal.yml

Look at Kubernetes objects created after this command:

kubectl get all

Wait for all the components to be up and running. Get the external IP address of the web service and try to connect to the application, in the same way you did in the previous section.

If you can play with the application like you did in your local deployment it means that you reached the conclusion of this assignment! Bravo!

The next exercise is optional.

If you don’t intend to do it, make sure to read the conclusion of this document to take down the application and remove all resources!!.