We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What version of descheduler are you using?
descheduler version: 0.23.0
Does this issue reproduce with the latest release? Yes
Which descheduler CLI options are you using? Helm installation is used. In values.yml, some of the cmdOptions are not valid anymore.
cmdOptions: v: 3 # evict-local-storage-pods: # max-pods-to-evict-per-node: 10 # node-selector: "key1=value1,key2=value2"
Please provide a copy of your descheduler policy config file Default policy config is used.
What k8s version are you using (kubectl version)?
kubectl version
$ 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:"22", GitVersion:"v1.22.3", GitCommit:"c92036820499fedefec0f847e2054d824aea6cd1", GitTreeState:"clean", BuildDate:"2021-10-27T18:35:25Z", GoVersion:"go1.16.9", Compiler:"gc", Platform:"linux/amd64"}
What did you do? I added some of the parameter which are described here. To fix it, we need to provide parameters along with deschedulerPolicy.
deschedulerPolicy
deschedulerPolicy: maxNoOfPodsToEvictPerNode: 20 ignorePvcPods: true strategies:
What did you expect to see? Pod should be in Running state
What did you see instead? Pod cannot run and prints out the descheduler --help output.
descheduler --help
cc. @necatican @f9n @developer-guy @Dentrax @yasintahaerol
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
What version of descheduler are you using?
descheduler version: 0.23.0
Does this issue reproduce with the latest release?
Yes
Which descheduler CLI options are you using?
Helm installation is used. In values.yml, some of the cmdOptions are not valid anymore.
Please provide a copy of your descheduler policy config file
Default policy config is used.
What k8s version are you using (
kubectl version
)?kubectl version
OutputWhat did you do?
I added some of the parameter which are described here. To fix it, we need to provide parameters along with
deschedulerPolicy
.What did you expect to see?
Pod should be in Running state
What did you see instead?
Pod cannot run and prints out the
descheduler --help
output.cc. @necatican @f9n @developer-guy @Dentrax @yasintahaerol
The text was updated successfully, but these errors were encountered: