NOVEMBER 6 – 9 – Chicago (IL)
Conference Website
Take a look for yourself:
Executing a blackhole attack on a Kubernetes deployment
Youtube content is not loaded per default for privacy reasons.
Ben Blackmore – Staff Software Engineer at Steadybit
1.
Identify all the dependencies in your cluster. Doing this is crucial information to determine the necessary experiments to conduct.
Steadybit discovers static and dynamic data from your kubernetes cluster to provide you a precise picture. If you want to go further, you can use our policies and visualize the coverage of your resilience tests and quickly identify kubernetes misconfigurations.
2.
In the centralized execution view, you will get helpful information out-of-the-box for your state checks (e.g. verify pod count) and Kubernetes events. This allows you to see all effects on your system.
Having the information in one place makes it easy to correlate the actions with their impact.
3.
Use valuable data from your monitoring tools (such as prometheus) for state checks and visualize it in the execution view. This helps you to better understand what's going on and allow you to use the same checks you're using for alerting.
Your load tests can prove very useful in chaos experiments. Either run them directly from Steadybit or trigger experiments from them.
Need to integrate a tool missing on our list? Steadybit is fully extensible!
4.
To strengthen your system, verify your changes before they hit production. Integrate Steadybit into your CI/CD pipeline using our CLI, HTTP API, or Github Actions. So you won't be surprised with your next release.
