brianberzins

I'm pretty sure this is exactly what I just ran into. For anyone else trying to figure out what's happening, in kubernetes 1.17.0 deployments moved from beta into `app/v1` From...

Honestly, I'm a bit confused here... because I don't understand why this would be working in 1.16 either... because it looks like `extensions/v1beta1/deployments` was removed in 1.16.0... I'm still digging...

@jdharmon I've done that on other projects before, and I think it's a great idea here. I additionally want to make it extremely easy to spin up a test cluster...

I was wondering if/when this would ever come back to bite me... https://github.com/target/pod-reaper/issues/37 Long story short... "status" as listed by kubectl isn't either pod-phase or reason... it's actually something different......

I'm going to have to check this one out in a lot of detail based on how my local development environment didn't like this. First thing I noticed is that...

got a little time to look at this, and things are working MUCH better in my local environment now. Honestly, I was expecting there to be something deep wrong with...

currently trying to figure out why this isn't working in my local environment - `docker build .` fails with: ``` ... ---> Running in 2300071fdad4 vendor/github.com/Azure/go-autorest/autorest/adal/token.go:39:2: cannot find package "github.com/form3tech-oss/jwt-go"...

uhg... that's almost certainly my bad...

Notes from #46 1. Documentation about how rules work needs to be updated here 1. Failing fast on invalid configurations (at least on the pod-reaper side) It isn't possible to...

Functionally, I'm feeling pretty dang good about this right now. Can try it out from my latest commit here: brianberzins/pod-reaper:alpha-20200227 @jdharmon I realized I had included more debug logging before...