Running Failed Scheduled Experiments
In this lesson, we will simulate a failed experiment by deleting the Deployment. Moreover, we will also discuss how to generate a report for it.
Deleting the Deployment to simulate a failed experiment
Let’s see what happens when an experiment fails. You probably already know the outcome, or, at least, you should be able to guess. Nevertheless, we’ll simulate a failure of the experiment by deleting the Deployment go-demo-8. As a result, the Pods of the application that is used as the target of the experiment will be terminated, and the experiment will inevitably fail.
kubectl --namespace go-demo-8 delete deployment go-demo-8
Retrieving pods created by CronJobs
The target of the experiment (the application) is gone. We’re going to retrieve the Pods of the experiment created by the CronJob.
kubectl --namespace go-demo-8 get pods --selector app=go-demo-8-chaos
Keep repeating that command until the output is similar to the one that follows. Remember, new experiments are being created every five minutes. On top of that, we need to wait for a minute or two until the chaos process finishes running. ...