Let’s face it, bad things happen in software engineering, often when you least expect it. Servers go down, there are spikes in traffic, you receive networking errors. Luckily, you can avoid these problems. Enter chaos engineering.
Chaos engineering is where you try to find the limits of a system and simulate adverse effects that might happen. These simulations then help you to determine the best way to improve your system and build up its resiliency.
This course is divided into various sections to get you used to the different types of experiments you can run in chaos engineering. You will start by learning how to destroy application instances in order to show you the importance of scaling, fault tolerance, and high availability.
You will then dive deep into other types of experiments such as destroying a network, draining and deleting nodes, and testing availability. Towards the end of the course, you will learn how to run experiments in a Kubernetes cluster.

The DevOps Toolkit: Kubernetes Chaos Engineering

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.

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.

This lesson shows the step-by-step process of deploying a demo application.

Introduction To Kubernetes Chaos Engineering

Defining Requirements

Destroying Application Instances

Experimenting with Application Availability

Obstructing and Destroying Network

Draining and Deleting Nodes

Creating Chaos Experiment Reports

Running Chaos Experiments Inside a Kubernetes Cluster

Executing Random Chaos

What’s Next?

Deploying the Application

Pulling the latest version of the repository