Closed arousseau-coveo closed 8 months ago
Hi @arousseau-coveo we run integration tests against the current release and 2 previous versions so you are correct that v0.27 should work with Kubernetes 1.25, 1.26, and 1.27
I noticed that you left the kubectl version
empty. Would you be able to provide your server version so I can make sure we're parsing it correctly? Thanks!
Hi @arousseau-coveo we run integration tests against the current release and 2 previous versions so you are correct that v0.27 should work with Kubernetes 1.25, 1.26, and 1.27
I noticed that you left the
kubectl version
empty. Would you be able to provide your server version so I can make sure we're parsing it correctly? Thanks!
@a7i I just added the output now I feel it's because of how EKS format the versions that we have that message.
Thank you for raising this and providing the data.
I should be able to get a fix soon and get it out in the next patch or minor release.
What version of descheduler are you using?
descheduler version: 0.27.1
Does this issue reproduce with the latest release? Yes
Which descheduler CLI options are you using? N/A
Please provide a copy of your descheduler policy config file N/A
What k8s version are you using (
kubectl version
)? N/Akubectl version
OutputWhat did you do? N/A
What did you expect to see?
Clear information about version compatibility.
What did you see instead? The version compatibility matrix informations doesn't seems to reflect the current state of the descheduler.
The above sentence lets presume that 0.27 will works with k8s 1.27, 1.26,1.25 but while running 0.27 on k8s 1.25 we face the following warning:
Warning: Descheduler minor version 27 is not supported on your version of Kubernetes 1.25+. See compatibility docs for more info: https://github.com/kubernetes-sigs/descheduler#compatibility-matrix
Also
Let presume descheduler version 0.27 will not work for kubernetes version 1.25, 1.26, 1.27, 1.28 .... which is probably not the case.
So what information is correct here ?