Jason Harmon

How about an option to read the local kubeconfig? Then you could run/debug pod-reaper locally. See [Authenticating outside the cluster](https://github.com/kubernetes/client-go/tree/master/examples/out-of-cluster-client-configuration).

I tried to write e2e tests this weekend after reading [Kubernetes End-to-end Testing for Everyone](https://kubernetes.io/blog/2019/03/22/kubernetes-end-to-end-testing-for-everyone/) and using https://github.com/kubernetes-sigs/descheduler/blob/master/test/e2e/e2e_test.go as an example. Their basic process is: ``` kind create cluster docker...

The [Visual Studio Code Remote - Containers](https://code.visualstudio.com/docs/remote/containers) looks like it could be a good option. There is a Go demo: https://github.com/Microsoft/vscode-remote-try-go

Perhaps the way forward is 1. Rename current pod_status rule to pod_status_reason, and change the environment variable to `POD_STATUS_REASON` 2. Add pod_status_phase rule with environment variable `POD_STATUS_PHASE`

I did move things around based on [Standard Go Project Layout](https://github.com/golang-standards/project-layout#standard-go-project-layout). * `main` moved from `/reaper` to `/cmd/pod-reaper` * `rules` moved from `/rules` to `/internal/pkg/rules` I initially planned to factor...

I just looked, and realized `/cmd` didn't get committed. Sorry. Will fix it tonight.

You could run without make. ``` ./test/create-cluster.sh e2e ./test/run-e2e-tests.sh ```

I added tests for chaos, unready, and duration rules. I chose to implement them outside of a container as it provides more control and gives the option of debugging. There...

I didn't see that the Dockerfile was changed in master. I will update and push a fix.

@brianberzins Make sure you pull the latest from STIHLDev:e2e. It looks like you're still using glide for dependencies.