Chris Love

@chrisseto thoughts on this issue?

@udnay @johnrk lets use this issue to determine our support matrix and branching policy

Documentation to help with this https://github.com/kubernetes/community/blob/master/contributors/devel/sig-release/cherry-picks.md Another component figuring out a support matrix https://github.com/kubernetes-sigs/descheduler/issues/273 This is way more than needed, but we can probably use snippets of this https://github.com/kubernetes/sig-release/tree/master/release-engineering/role-handbooks

Kops versioning https://kops.sigs.k8s.io/welcome/releases/

Here is how k8s does tagging https://github.com/kubernetes/sig-release/blob/master/release-engineering/versioning.md

We are going to need to update to controller-runtime 0.9.x on a new branch and put the current master on a new branch as well. We are going to need...

Well this is gonna be tough since the code uses `AmazonEC2FullAccess`

@udnay Please document what the correct workflow is for decommision. We are getting differing opinions.

@udnay this needs manual testing, but removing release blocker

@rail I need to implement this in bazel and test it. This is on my plate after I get my current PRs wrapped up.