Deploying the Application

The only thing left for us to do, before we dive into reporting, is to deploy the demo application. It’ll be the same one we used before, so what follows will not be a mystery. Let’s go through it fast.

Pulling the latest version of the repository#

We’ll go to the go-demo-8 directory and pull the latest version of the repository.

Creating a namespace and adding a label for Istio#

Next, we’ll create a Namespace called go-demo-8 and add the label so that Istio knows that it should inject proxy sidecars automatically.

Applying the definition#

We’re going to apply the definition from the directory k8s/app-full and, once all the resources are created, we’re going to wait until the Deployment of the API rolls out.

Sending a request to confirm accessibility#

Finally, to be sure that it works fine, we’re going to send a request to the newly deployed demo application.

Now, we are ready to generate some data based on experiments. Once we have the information we need, we will try to figure out how we can generate reports. After all, you’ll need something like a PDF document to give to your manager and make them happy. More importantly, we want to generate something that you can give to the rest of the teams. It should contain, in a digestible format, information about what’s wrong, what failed, and what was successful in chaos experiments.

The next lesson will contain the instructions on how to create a journal file with information generated during experiments.