Steadybit helps you in your path to a resilient system by analysing the configuration of your deployed environment and suggesting improvements to make it even more resilient. This way, you can fast-forward and don't need to execute an Experiment for learning your system. In addition, you can also use the weak spots as part of a Policy.
We currently support some weak spots for Kubernetes, AWS, Azure and Java.
Kubernetes Weak Spots
Why is it important for a resilient system?
Checks whether the consumption of the CPU is limited for a Kubernetes deployment.
When your deployment uses too much CPU other deployments on the same node could become unstable.
Ensures that your configuration prevents a Kubernetes deployment to consume more memory than configured.
When your deployment uses too much memory other deployments on the same node could become unstable.
Verifies that at least two PODs of the same deployment exists.
It is hard to make single source of failure (like a single POD) resilient.