deadpool restarts unresponsive EC2 instances.

You will need to run the server as an appropriately privileged user. The privileges you need depend on the monitoring plugins you use. See policy_template.json for an AWS policy template for an AWS policy that has the needed privileges for most cases.

See example_config.yaml for reference. It is fairly extensively commented. Adjust it to suit your needs, then save it as /etc/deadpool.yaml.

deadpool currently decides whether an EC2 instance is unresponsive by consulting an OpenShift cluster via the Kubernetes API. It assumes that the node name in OpenShift/Kubernetes corresponds to the EC2 instance's private DNS name. (This is the recommended way of naming nodes when running OpenShift on EC2.)

If you have your configuration file saved as /etc/deadpool.yaml, then just run deadpool. If not, then run deadpool --config /path/to/config/file. You can also run with --dryrun to prevent it from making changes to EC2 instances.

The included Dockerfile runs deadpool with --config /etc/deadpool/deadpool.yaml. The idea is that you mount a directory containing deadpool.yaml at /etc/deadpool inside the container. This also makes it ideal for running on OpenShift; deadpool.yaml can be stored as a secret and mounted at /etc/deadpool by the usual mechanism.

To hit the health check endpoint, do this: curl -H "Authorization: $SECRET_KEY" http://deadpool.example.com/health. $SECRET_KEY should match the secret_key you set in the configuration file.

deadpool uses glide to wrangle dependencies. Install it first.

To install dependencies, just run glide install.

To build, run make (or make linux|osx|windows to build for just one platform).

Many thanks to my employer, Exosite, which gives its employees the freedom to open-source broadly useful tools like this.