Release v0.10.0

[seanmalloy]

It has been quite a while since the last scheduler release. I am proposing that descheduler release v0.10.0 is created in the near future. See below list of suggested pull requests that I think should be merged before the v0.10.0 release is created.

• Implement --descheduling-interval CLI option Wire --descheduling-interval to run descheduler on a loop #221
• Automated Container Image Builds Automate Container Image Builds Using GCB #217
• Automated Container Image Builds Part 2 Add Image Push Job For Descheduler kubernetes/test-infra#16022
• Switch to Go modules Remove k8s.io/kubernetes deps and switch to go modules #216
• Documentation updates Streamline Deployment Docs For End Users #208
• Build automation clean up Fix makefile for make gen, and update hack files and auto-generated files. #236

Additionally this would be the first release where an official container image for descheduler can be pushed to gcr.io.

Normally I would create a milestone for tracking this stuff, but I don't have access to create/update milestones in the repo. So this is the best alternative I could come up with.

[seanmalloy]

@ravisantoshgudimetla @aveshagarwal @damemi let me know if you think this is a reasonable proposal.

Also ...

I think I can help out by reviewing #216 in the near future and I will also sign up for writing the release notes for v0.10.0. Let me know if there is anything else I could do to help with this.

[damemi]

Thanks @seanmalloy, definitely +1 to this.

It would also be nice if we could start tagging regular releases to coincide with our bumps for kubernetes versions. Maybe even use a matching version scheme like v0.10.18->k8s 1.18, etc.

[seanmalloy]

Rough draft of release notes. I'll probably review and revise these at least one more time myself, but if anyone else has any suggestions that would be cool too.

New Features 🌈

• Users can specify pods that are safe to evict using annotation descheduler.alpha.kubernetes.io/evict - Evict annotation #186
• Create k8s events when pods are evicted - Add k8s events support #183
• New strategy RemovePodsViolatingNodeTaints - Strategy to consider taints and tolerations in Descheduler #175
• Implement CLI option --descheduling-interval - Wire --descheduling-interval to run descheduler on a loop #221

Bug Fixes 🐛

• Fix duplicate strategy to also take namespace into account - Added ownerRef.UID for evaluating duplicate Pods #156
• Spelling fix - Fix small typo in output for thresholds #178
• Fix typos in k8s yaml files - Fix typos in kubernetes example #193, Fix intentation on yaml #201

Others 🏃

• Enable golangci-lint - Adding golang ci lint support and Refactoring test by make it table driven #149
• Setup official Google Container Registry descheduler container image - Push Container Images To k8s.gcr.io #160, Use correct GCR staging registry #173, Automate Container Image Builds Using GCB #217
• Improve duplicate strategy unit tests - Improved logic for duplicates testing #162
• Enable e2e tests in TravisCI - Remove hardcoded node selection in E2e test  #169
• Migrated to kubernets-sigs GitHub organization - Project migrated under kubernetes-sigs, change import path prefix to sigs.k8s.io/descheduler #182
• Clean up golint - Fix golint errors #190
• Switch from glog to klog - Switch from glog to klog #192
• Bump k8s dependencies to v1.17 - Bump k8s deps to 1.17 #204
• Update to Go 1.13 - Update To Go 1.13.5 #209
• Update k8s yaml files to use priorityClassName instead of critical-pod annotation - Update examples to support v1.16.0+ #213
• Use Go modules instead of glide - Remove k8s.io/kubernetes deps and switch to go modules #216

[damemi]

These release notes look good. #221 just merged so you can add that to the notes and cross it off in your original post. I'd like to get everything else in your first post finished too, hopefully before the 1.18 release of k/k

[aveshagarwal]

@seanmalloy release notes looks really good. thanks.

[ravisantoshgudimetla]

I agree with @damemi and @aveshagarwal on the release notes. This is really good. Thanks for working on this @seanmalloy

[seanmalloy]

Just one more PR to review and merge for the v0.10.0 release, #208.

Here is a gist with the updated release notes. This should provide an easy copy and paste for the person that creates the release.

https://gist.github.com/seanmalloy/3ae02ebdad8519db0d2dddb3f36bb471

[aveshagarwal]

thanks a lot @seanmalloy and @damemi for your work on this release.

Would like to know your thoughts what you think if instead of making 0.10.0, we release 1.0.0?

[damemi]

I would like to get this to 1.0.0 as soon as we can, but I think we should first promote our APIs out of alpha before bumping to a major version release. Wdyt?

[seanmalloy]

I agree with @damemi. We have a some work to do before we are ready for v1.0.0. I think for now it would be best to stick with v0.10.0.

[aveshagarwal]

ok sounds good. Please let me know if we are ready and i will cut a release v0.10.0.

[aveshagarwal]

would like to get this PR: #236 in before we cut a release.

[seanmalloy]

@aveshagarwal I'm not aware of anything else that needs to be merged prior to cutting the release. Let me know if you need any help with the release process.

[aveshagarwal]

@seanmalloy as per the release process doc and semi auto section, i have completed first 3 steps. Feel free to go for other steps. Let me know if my help is needed.

[seanmalloy]

@aveshagarwal here is the PR for step 4 ... kubernetes/k8s.io#570.

[aveshagarwal]

@aveshagarwal here is the PR for step 4 ... kubernetes/k8s.io#570.

i have lgtm'ed, i am not sure if i can /approve too in that repo.

[seanmalloy]

i have lgtm'ed, i am not sure if i can /approve too in that repo.

@aveshagarwal you have been added to the OWNERS file here, so for future releases both you and @ravisantoshgudimetla will be able to approve descheduler image promotions.

Step 4 is done the image is available at us.gcr.io/k8s-artifacts-prod/descheduler/descheduler:v0.10.0.

@aveshagarwal you can go ahead and complete the last two release steps, 5 and 6.

[aveshagarwal]

@seanmalloy thanks a lot for your help. I have published v0.10.0 now so step 5 is done now. Feel free to go for step 6.

[seanmalloy]

@aveshagarwal I'll do the 6th and final step. Thanks for your help!

[mattlqx]

FYI the release notes at https://github.com/kubernetes-sigs/descheduler/releases are incorrect as they state the image as us.gcr.io/k8s-artifacts-prod/descheduler:v0.10.0 and not us.gcr.io/k8s-artifacts-prod/descheduler/descheduler:v0.10.0.

[seanmalloy]

@aveshagarwal I had the incorrect image location in the release notes. Sorry about this. Can you edit the release notes to change the location of the container image to be us.gcr.io/k8s-artifacts-prod/descheduler/descheduler:v0.10.0?

https://github.com/kubernetes-sigs/descheduler/releases/tag/v0.10.0

I completed step 6(send email). I'll close out this issue once the typo is fixed in the release notes.

[aveshagarwal]

@seanmalloy fixed the path.

[seanmalloy]

/close

Thanks for your help @aveshagarwal!

[k8s-ci-robot]

@seanmalloy: Closing this issue.

In response to this:

/close

Thanks for your help @aveshagarwal!

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.