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

So far, we’ve been unleashing chaos on our applications and networking. That's been very enlightening, at least to me. But there is still a lot that we should and that we can do.

One big topic that we haven't touched yet is related to nodes. 

* What happens if there is something wrong with the nodes of our cluster?
* What happens if suddenly all the applications running in a node disappear?
* What happens if a node goes down or if it's destroyed? 

Those are the subjects we'll explore in this section. We're going to try to figure out how to create chaos that will generate issues related to nodes of our cluster. 

---

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 carry out experiments of issues related to nodes.

Overview