Skip to content

chaosrancher periodically kills random services in your Rancher Stack/Cluster.

License

Notifications You must be signed in to change notification settings

bscott/chaosrancher

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

10 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

chaosrancher

Docker Repository on Quay

Why

Test how your system behaves under arbitrary service failures.

Setup

ChaosRancher reads from enviroment varibles to authenticate to Rancher API (v2-beta is only supported at the moment, v1 is not)

# Set the url that Rancher is on
$ export RANCHER_URL=http://<server_ip>:8080
# Set the access key, i.e. username
$ export RANCHER_ACCESS_KEY=<accessKey_of_account_api_key>
# Set the secret key, i.e. password
$ export RANCHER_SECRET_KEY=<secretKey_of_account_api_key>

Example

Running it will kill a service in any stack every 10 minutes by default.

$ chaosrancher

or Deploy ChaosRancher in Rancher's Sandbox environment:

Try Rancher

Filtering Services

To select a specific environment that should be targeted:

# Set the environment to use, you can use either environment ID or environment name
$ export RANCHER_ENVIRONMENT=<environment_id>

Contributing

Feel free to create issues or submit pull requests.

About

chaosrancher periodically kills random services in your Rancher Stack/Cluster.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages