Daniel Albuquerque
Daniel Albuquerque
Hi @jpittis. Thanks for the feedback. This would be used in a staging/test environment, not in a production one.
Hi Jake! Yes and no. I managed to use Kubernetes config maps feature to pass the config file to Toxiproxy. Given that this would have been a breaking change (with...
Yeah, sorry about that @jpambrun :( I needed some extra features so I kinda butchered the project in that branch. I'll reopen this pr (didn't know it could be of...
> I would replace ability to load config via ENV variable instead. Currently I am not fully convinced to change the arguments. > > ENV is good, that it is...
I created an http toxic, based on the work from @xthexder, so that I could modify the host header. I can open a pr with this if you'd like, as...
Hi @maxgalbu! If you forked my repo then make sure you use the branch **http_toxic** and not master, as the master has other changes that have not been tested (some...
@maxgalbu just clone my repo, checkout the branch http_toxic and run `make clean && make build && make linux && make docker` If you want you can pull this docker...
Hi folks! Is there still interest in this?
We already use github pages as a way to publish helm charts (https://github.com/asobti/kube-monkey/tree/gh-pages) but I'm sure we can have them for both charts + docs. I've used mkdocs material in...
This looks interesting but very inflexible. With the suggested approach you can only run the same exact attack against all your victims. It seems a bit odd to use annotations...