Helm chart some cmdOption are not supported.

[eminaktas]

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 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:"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:
  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.

cc. @necatican @f9n @developer-guy @Dentrax @yasintahaerol