kube-monkey
kube-monkey copied to clipboard
asobti
An implementation of Netflix's Chaos Monkey for Kubernetes clusters
While the existing README is a great start, this project can use a documentation site since it's growing fast (Yayy!!) Options: 1. https://argo-cd.readthedocs.io/en/latest (readthedocs) 2. https://github.com/kubernetes/website (GitHub/Netlify), Hugo/GitHubPages, or other...
My app has many many deployments, it would be tedious to have to modify all of them. Can we instead have some annotations on a namespace. I'd like my dev...
I have deployed the kube-monkey in default namespace and following is my configuration. root@k8s master0 ]# kubectl get po + kubectl get po NAME READY STATUS RESTARTS AGE kubemonkey-kube-monkey-57b6d94c-2lmbs 1/1...
Could you append this func into your main.go and update the go.sum?? I believe this will fix the issue trying to kubectl exec into the pod to check the config.toml...
This PR change the defination of "kube-monkey/mtbf". When we use kube-monkey to kill pod in k8s cluster, we find it too slow to generate a failure, because the label 'kube-monkey/mtbf'...
Hello, I am facing similar issue which you already close it before #80. However, I am working on it from past few days and I am not able to solve...
https://github.com/asobti/kube-monkey#example-of-opted-in-deployment-killing-one-pod-per-purge Currently these need to be set at both **metadata.labels** and **spec.template.metadata.labels**. This can lead to conflicting configurations where we have different values in each of these. It also means...
This is `config.toml` sample from the docs: ``` [kubemonkey] dry_run = true # Terminations are only logged run_hour = 8 # Run scheduling at 8am on weekdays start_hour = 10...
timeZone in values-yaml not working as expected. For instance it prints 06/28/2020 13:49:00 +0200 CEST in logs even if i set some CET time zone from https://golang.org/src/time/zoneinfo_abbrs_windows.go
I tried kubemonkey on a deployment. Applied the following to deployment, made sure even the pods under the deployment gets propagated to the pods as well and kubemonkey picked up...
