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

Generally speaking, there are two ways we can run experiments. Or, to be more concrete, we'll explore two even though are certainly other methods.

# One-Shot experiments

We can run one-shot experiments by executing experiments on demand. We can say, "let's run that experiment right now." I'm calling them "one-shot" because such experiments would not be recurring. We'll be able to choose when to execute them, and they will exist only while they're running. We'll be able to monitor the progress and observe what's going on. We could run those experiments manually, or we could hook them into our continuous delivery. In the latter case, they would be part of our pipelines and, for example, executed whenever we deploy a new release.

# Scheduled experiments

Later on, we're going to explore how to create scheduled experiments that will run periodically. We might choose to do chaos every few minutes, every few hours, once a day, or whatever the schedule we'll define is.

---

The next lesson will cover the execution of one-shot experiments.


This lesson briefly explains the two types of experiment executions.

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?

Types of Experiment Executions