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

# Things to keep in mind
The course is about to start unfolding. We are about to dive into chaos engineering.
For now, please assume that anything can fail. That’s the most important thing you should remember. It should be engraved in your brain that whatever can fail is likely to fail.
We are going to start small and expand over time. The first exercises might seem too basic. That’s intentional. I want you to start small and to grow over time.

I want you to communicate with your colleagues. That is probably the most important thing in chaos engineering. It is essential that the lessons learned and the lessons that you will apply in your own system are communicated with the rest of your company, with your teammates, with your colleagues. It is vital that you all collaborate in solving the issues you will find.


I highly encourage you to join the [DevOps20 Slack workspace](http://slack.devops20toolkit.com). We are there, and we’ll do our best to answer any questions and help with any issues that might arise.

Finally, there is a [mailing list](http://eepurl.com/bXonVj) that you might want to subscribe to if you wish to receive notifications when we write new courses, books, and publicly accessible material.


---

In the next chapter, we will define the requirements of this course and install the necessary tools.


This lesson contains some last pointers for getting started with the course.

Before We Begin

Things to