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 need to have a cluster where we'll run the demo application as well as the experiments. Whether you have it or not depends on whether you destroyed your cluster at the end of the previous section. If you didn't destroy it, just skip to the next section right away. If you did destroy the cluster, feel free to use one of the Gists that follow to create a new one. Alternatively, you can roll out your own cluster. It's up to you.

## Gists for different Kubernetes flavors

* [Docker Desktop with Istio](https://gist.github.com/9a9752cf5355f1b8095bd34565b80aae)
* [Minikube with Istio](https://gist.github.com/a5870806ae6f21de271bf9214e523b53)
* [Regional and scalable GKE with Istio](https://gist.github.com/88e810413e2519932b61d81217072daf)
* [Regional and scalable EKS with Istio](https://gist.github.com/d73fb6f4ff490f7e56963ca543481c09)
* [Regional and scalable AKS with Istio](https://gist.github.com/b068c3eadbc4140aed14b49141790940)

---

The next lesson will contain the instructions for deploying the demo application.

We need to have a cluster where we'll run the demo application as well as the experiments. Whether you have it or not depends on whether you destroyed your cluster at the end of the previous section. If you didn't destroy it, just skip to the next section right away. If you did destroy the cluster, feel free to use one of the Gists that follow to create a new one. Alternatively, you can roll out your own cluster. It's up to you.

# Gists for different Kubernetes flavors

* [Docker Desktop with Istio](https://gist.github.com/9a9752cf5355f1b8095bd34565b80aae)
* [Minikube with Istio](https://gist.github.com/a5870806ae6f21de271bf9214e523b53)
* [Regional and scalable GKE with Istio](https://gist.github.com/88e810413e2519932b61d81217072daf)
* [Regional and scalable EKS with Istio](https://gist.github.com/d73fb6f4ff490f7e56963ca543481c09)
* [Regional and scalable AKS with Istio](https://gist.github.com/b068c3eadbc4140aed14b49141790940)

---

The next lesson will contain the instructions for deploying the demo application.

This lesson contains instructions regarding creating 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?

Creating a Cluster

Gists for different Kubernetes flavors