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

We saw that we could run experiments targeting applications running in Kubernetes. We messed with networking, and we saw how to shut down and manipulate nodes of a cluster. However, we were doing all that by running experiments locally. Our experiments were targeting a remote Kubernetes cluster.

What we have done so far was useful as a way to figure out how chaos experiments work. Now is the time to move the execution of those experiments away from our laptop and into a Kubernetes cluster. In addition to targeting a Kubernetes cluster, we want to run the experiments inside it and target the components inside the same cluster where chaos experiments are running.


In this section, we are going to explore how to transfer the execution of our chaos experiments from our laptops into a Kubernetes cluster.

---

In the next lesson, we will be provided with a gist that contains all the commands for this chapter.


This lesson defines the goal of this chapter which is to transfer the execution of our chaos experiments from our laptops into a Kubernetes cluster.

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?

Overview