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

Just as before, at the end of each section, we'll delete everything we did.


We went one directory back and deleted the Namespace.

Unlike other sections, this time, destroying the cluster is probably not optional. We removed a node in a cluster that was not auto-scalable, and that is a terrible idea. We could modify the cluster to be auto-scalable and regional, but that would be too much work. Instead, make sure that this time, you destroy the cluster, even if you’re not taking a break. Starting from the next section, we will be creating a cluster in a much better and more resilient way, making it regional and scalable.


---

In the next chapter, we will learn how to create informative reports of the chaos experiments.

This lesson contains the instructions on how to delete the used resources to free up space.

Destroying What We Created