Level-up your testing with Chaos Engineering. Learn how pushing your programs to failure can help you plan your improvements.

DevOps for Developers

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.

Kubernetes Chaos Engineering

As always, we will need a cluster. However, this time, it is going to be a bit better defined than before. In the previous section, we gained some insights that should help us create a more robust cluster. It will be regional and scalable. Or, to be more precise, it will be like that if that's possible. 

# Note for Minikube and Docker Desktop users

If you're using Docker Desktop or Minikube, it will not be regional nor scalable because those are single-node clusters. Nobody's perfect.

# Istio Ingress Gateway

Just remember that, no matter how you create the cluster, we will need the `INGRESS_PORT` variable with the Istio Ingress Gateway address. That, as you can probably guess, means that the cluster should have Istio up-and-running.

# Gists for different Kubernetes flavors

Gists with the commands to create and destroy a Kubernetes cluster are as follows.

* [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)

Now that we have a cluster, we'll deploy our demo application. And, after that, we'll be able to run some experiments. This time, we will not run them for the sake of exploring new ways to destroy stuff. Instead, we'll run experiments so that we can gather some data which we'll use to generate reports.

---

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



This lesson contains instructions regarding creating a Kubernetes cluster.

Creating a Cluster