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

## What is chaos engineering? 

**We can describe chaos engineering as a discipline of experimenting on a system to build confidence in the system's capability to withstand turbulent conditions in production.** Now, if that is too confusing and you prefer a more straightforward definition of what chaos engineering is, I can describe as **being prepared because bad things will happen**. It is inevitable.


## What are the principles behind it?

Bad things happen, often, when we don’t expect them. Instead of being reactive and waiting for unexpected outages and delays, we employ chaos engineering and to simulate adverse effects that might occur in our system. Through these simulations, we can learn what the outcomes of our experiments are and how we can improve our system by making it resilient and by trying to design it in a way that it is capable of withstanding unfavorable conditions in production.


---

In the next lesson, we will discuss if you are ready for carrying out chaos experiments or not.

# What is chaos engineering? 

**We can describe chaos engineering as a discipline of experimenting on a system to build confidence in the system's capability to withstand turbulent conditions in production.** Now, if that is too confusing and you prefer a more straightforward definition of what chaos engineering is, I can describe as **being prepared because bad things will happen**. It is inevitable.


# What are the principles behind it?

Bad things happen, often, when we don’t expect them. Instead of being reactive and waiting for unexpected outages and delays, we employ chaos engineering and to simulate adverse effects that might occur in our system. Through these simulations, we can learn what the outcomes of our experiments are and how we can improve our system by making it resilient and by trying to design it in a way that it is capable of withstanding unfavorable conditions in production.


---

In the next lesson, we will discuss if you are ready for carrying out chaos experiments or not.

In this lesson, we will define chaos engineering and the principles behind it. 

Before We Begin

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

Conclusion

Principles of Chaos Engineering

What is chaos engineering?