Delve into Kubernetes Chaos Engineering to discover system limits, simulate adverse effects, and improve resiliency. Learn about fault tolerance, high availability, and running experiments in a Kubernetes cluster.

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

Chaos Toolkit allows us to create a journal file with information generated during an experiment.

# Using the definition of `health-http.yaml`

To generate data, we need to run an experiment. Let's take a look at the definition of a familiar one.


We have already explored that experiment, so there's probably no need to go through it. Even if you forgot it, you should have enough experience to deduce what it does yourself. Remember, the subject of this section is not to learn new ways to define experiments and destroy stuff, but to create reports. For that, we need data or, if we switch to Chaos Toolkit terminology, we need a journal.

# Running chaos experiment with the `--journal-path` argument

We'll run the experiment in a similar way as before, but with a twist.

In this lesson, we will re-run an experiment as we did before, but this time we will generate a journal file for it which is stored in JSON format.

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?

Exploring Experiments Journal

Using the definition of `health-http.yaml`