You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One question, @Lawouach , what are your thoughts on where the experimental outcome from the job should go? And can we grab an experiment from a git repo directly (a URL), such as:
$ chaos run https://github.com/chaostoolkit/chaostoolkit-samples/tree/master/experiments/my-experiment.json
As for where the results may go, it's a very good question. I guess, we could rely on a new chaostoolkit-event plugin (ala chaostoolkit-slack), that uploads it where it fits the user needs?
I like the idea of mounting a Git Repo volume, that sounds more "native" and possibly less of a security "hole" than "run any experiment reachable from a URL"?
For example, with the latter we might have to worry about whitelists?
Taking inspiration from the existing Docker-based chaos runner here: https://github.com/chaostoolkit/chaostoolkit/blob/master/Dockerfile
The plan is to implement a Kubernetes Job that will be able to run (periodically?) a Chaos Experiment.
The text was updated successfully, but these errors were encountered: