kube-chaosmonkey
kube-chaosmonkey copied to clipboard
Published
20 hours ago •
cheyang
cheyang
kube-chaosmonkey
This kills pods to help check your environment can withstand failures by using fabric8 chaos monkey without fabric8 dependency
Run as a shell
- You need to specify a couple of environment variables for the container.
| Environment Variable | Description | example |
|---|---|---|
| KUBERNETES_MASTER | The URL to kubermaster | http://127.0.0.1:8080 |
| KUBERNETES_NAMESPACE | The name space of the pod to delete randomly | default |
| CHAOS_MONKEY_INCLUDES | regular expressions which can be splited by , | zk*,kafka* |
| CHAOS_MONKEY_EXCLUDES | regular expressions which can be splited by , | zk*,kafka* |
| CHAOS_MONKEY_KILL_FREQUENCY_SECONDS | The frequency to call the chaos monkey(seconds) | 30 |
-
Start chaos monkey docker container
docker run -d \ --name chaos-monkey \ e KUBERNETES_MASTER=http://127.0.0.1:8080 \ e KUBERNETES_NAMESPACE=default \ e CHAOS_MONKEY_INCLUDES=zookeeper*,kafka* \ e CHAOS_MONKEY_EXCLUDES=zk2* \ e CHAOS_MONKEY_KILL_FREQUENCY_SECONDS=30 \ abric8/chaos-monkey:2.2.115 -
Checking the logs of chaos monkey docker container
docker logs chaosmonkey 02:35:33 INFO #fabric8_default:34 - Chaos Monkey killed pod zk3-controller-uysjg in namespace default 2:35:33 INFO #fabric8_default:34 - http://i.giphy.com/OYJ2kbvdTPW6I.gif
Run inside the kubernetes
- Update env part of chaos-monkey-rc.yaml, it's the same as the shell
$ kubectl create -f kubernetes/chaos-monkey-rc.yaml
- Check the log of the container
$ kubectl logs chaos-monkey
You can ignore the error the following error as hubot is not available for fabric8 chat notifications:
Reason: java.lang.IllegalArgumentException: No kubernetes service could be found for name: hubot in namespace: default
cheyang