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 how we could rain destruction on many different levels.

We started small by destroying Pods. Then, we moved into destroying higher-level constructs and into measuring the health of our applications. We also messed with the network, nodes, and a few other things in between.

We’ll calm down for a while. We’ll stop the chaos, or at least, we will not create new types of destruction. Instead, we’ll focus on figuring out how to create informative reports that can be distributed throughout the company. Instead of creating more mayhem, we’ll figure out how we can create reports and  provide data to other teams that will inform them about the shortcomings of their applications and their clusters.


---

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 figure out how to create reports that contain informative data regarding the shortcomings of the 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?

Overview