Chaos Engineering

The library controller-runtime requires setting a logger (by log.SetLogger()) at the first 30s when the application starts, or it would use the default NullLogSink. We should also call it in testing codes.

When we test with ginkgo, ginkgo provides a helpful GinkgoWriter, which hides the output as default, only prints it when the test failed. We'd better use it to keep our testing output

Issue Description

Question

Describe what happened (or what feature you want)

Trying to evaluate ChaosBlade as an option for resiliency testing. But I'm not sure if this is a feature request or a question. Actually, two questions:

• Does ChaosBlade support Azure, or can it be extended to support Azure?
• Can ChaosBlade inject failures into a Platform as a Service (Pa

We can add an upgrade/downgrade command for litmusctl binary, it can look at the matrix of versions in a file and upgrade/downgrade according to the user's choice.

example

• litmusctl upgrade v0.5.0
• litmusctl downgrade v0.4.0

Running 2.9.1 (yes, I know, it's old). We have several different clusters, but don't have the same k8s deployments in each cluster. Tried to use a generic policy definition. When it is applied in a cluster which doesn't have one of the deployments, seal doesn't handle the 404 from k8s and dies. Yes, we can change the policies, but also seal shouldn't die in this scenario.

While this was wit

I try to run an experiment with variables configured in "configuration"
"configuration":{ "waitTime": 3 }
There it´s defined as Number
Then I want to use this var in pauses

"pauses":{ "after": "${waitTime}"}

This results into an error that pauses needs a Number
Can it be fixed that variables can be uses also in "pauses" ?

It would be good to try to rework the wait_for_ready_status function to use the kuberenetes client to get the node status

Line here to be re-worked: https://github.com/cloud-bulldozer/kraken/blob/7f6070144473ce5f1c2cf35e5192b0a88031d09b/kraken/node_actions/common_node_functions.py#L35