descheduler: Currently, v0.23.0 image has wrong app version

What version of descheduler are you using?

descheduler version: v0.23.0

crane digest k8s.gcr.io/descheduler/descheduler:v0.23.0
sha256:1a40adaa9b92624d09fee9e8611f0177949949c6f2fa633e43457eec96860c65

Does this issue reproduce with the latest release?

Yes.

Which descheduler CLI options are you using?

Default options.

Please provide a copy of your descheduler policy config file

Default policy yaml

What k8s version are you using (kubectl version)?

kubectl version Output

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4", GitCommit:"b695d79d4f967c403a96986f1750a35eb75e75f1", GitTreeState:"clean", BuildDate:"2021-11-17T15:48:33Z", GoVersion:"go1.16.10", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.7", GitCommit:"132a687512d7fb058d0f5890f07d4121b3f0a2e2", GitTreeState:"clean", BuildDate:"2021-05-12T12:32:49Z", GoVersion:"go1.15.12", Compiler:"gc", Platform:"linux/amd64"}

What did you do?

Nothing special.

What did you expect to see?

v0.23.0

What did you see instead?

v20220127-v0.22.0-79-gafb1d75ce

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 15 (15 by maintainers)

Most upvoted comments

is Merge helm chart update to release-1.xx branch node on the “Patch release” path marked as a “code changes” (blue) as well?

Correct, it’s technically both (a code change and a Helm release trigger) but I felt like it was more important to highlight that it was a release triggering action.

I’ll definitely add this to the docs, I think from what we learned in this release we could add some stuff to the checklist to make sure everything gets caught.

At this point though, I think we’ve resolved this issue. So I’m going to close it. Thanks again for reporting this @eminaktas ! /close

damemi on May 24, 2022

thanks for your update~ i will have a try now 😃

JaneLiuL on Mar 9, 2022