Deploying the Application

At the end of the previous section, we deleted the whole go-demo-8 Namespace. Now we need to deploy the application again. It will be exactly the same as the last version that we deployed before. With that in mind, we should be able to go through the deployment very fast.

Let’s deploy the application and go through this lesson fast. Let’s not waste time on that.

Pulling the latest version of the repository#

We are going to go to the go-demo-8 directory, the place where we have our local repository, and we’re going to pull the latest version of it just in case I made some changes.

Creating a namespace#

Next, we’re going to create the Namespace go-demo-8, and then we’re going to output the contents of the files in the terminate-pods/app directory.

The output of the latter command should display the same definitions as those we used in the previous section. So, there’s probably no need to go through it. It is the same app with the database and the go-demo-8 API defined as a Deployment. Nothing more, nothing less.

Applying the definition to the cluster#

So let’s apply this definition and wait until it rolls out.

It might take a while until the Deployment rolls out. Be patient and wait until the execution of the latter command is finished.

That’s it. The application is rolled out, and we can continue experimenting.

Later on, we’ll create some chaos on the cluster level. But, for now, we will be focused on applications.

Let’s see what else we can do. Can we prove that our application is highly available? Can we prove that it is not? That’s a mystery that is yet to be solved.

What do you think? Do you believe that the application we just deployed is highly available? And if you think it’s not, why do you think that?

In the next lesson, we will be verifying if our cluster is accessible from outside.