Mike Dame

@seleznev thanks for this, could you share the logs from the descheduler showing this eviction? Ideally at `v=4` log level. That should give us an idea about why it's doing...

Thanks @JaneLiuL and @pravarag, yes we should start preparing the 1.25 release with the `rc.0` tag bump

Thanks @JaneLiuL, what's the issue you're seeing? Let's continue that discussion in your PR

Updated the main comment here with a checklist for the pre-release actions For the next release, I'm thinking of organizing it with a [Github project](https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects), which basically just gives us...

@eminaktas you're not too late, but could you share where you're seeing that? When I run `descheduler version` I only see it in the `GitVersion`: ``` mikedame ~$ docker run...

At this point, I think we are all done with the pre-release steps (except for the helm chart update in https://github.com/kubernetes-sigs/descheduler/pull/936, which has to wait until [after we tag the...

That sounds good to me, I agree the metric should at least report the major+minor versions. Concatenating them into 1 label is probably good too. Do you think we can...

Anything else blocking this release? If not, I'm going to tag the new Git version, merge https://github.com/kubernetes-sigs/descheduler/pull/936, and start the image promotion PRs @ingvagabund @knelasevero @a7i @JaneLiuL @pravarag

Tag created, helm change merged, image promotion PR created at https://github.com/kubernetes/k8s.io/pull/4213, need approval there

Image promotion is done, helm chart releaser completed successfully, and release published at https://github.com/kubernetes-sigs/descheduler/releases/tag/v0.25.0! Just emailed sig-scheduling to announce it. Thanks everyone for another great release 🎉 /close