Aborting All Requests
Explore the impact of aborting all network requests in a Kubernetes environment. Understand how this chaos experiment reveals application failures and the importance of designing resilient applications that manage complete network outages effectively.
Sometimes, we’re unlucky, and we have partial failures with our network. At other times, we’re incredibly unfortunate, and the network fails entirely, or at least parts of the network related to one or a few of the applications are down. What happens in this case? Can we recuperate from that? Can we make our applications resilient even in those situations?
Inspecting the definition of network-abort-100.yaml and comparing with network-rollback.yaml
We can run an experiment that will validate what happens in such a situation. It’s going to be an easy one since we already have a very similar experiment.
Given that experiment is almost the same as the one before, and that you’d have a tough time spotting the difference, we’ll jump straight into the diff of the two.
The output is as follows.
51c51
<