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: v0.30.0
Does this issue reproduce with the latest release?
Yes.
Which descheduler CLI options are you using?
I'm using the helm chart v0.30.0
Please provide a copy of your descheduler policy config file
It's the default comming with the chart.
What k8s version are you using (kubectl version)?
kubectl version
$ kubectl version Client Version: v1.30.1 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.30.0+k3s1
What did you do?
I use the helm chart with the default options to deploy descheduler into my k8s cluster.
What did you expect to see?
Descheduler running successfully.
What did you see instead?
Descheduler throws config errors.
E0521 16:16:02.890228 1 run.go:74] "command failed" err="failed decoding descheduler's policy config \"/policy-dir/policy.yaml\": strict decoding error: unknown field \"nodeAffinityType\""
I will open a PR with my changes on the default profile.
The text was updated successfully, but these errors were encountered:
PR with possible fix: #1412
Sorry, something went wrong.
Fixed in #1412 - we'll work on getting a v0.30.1 out in the next week or so
it's in v0.30.1, thanks!
No branches or pull requests
What version of descheduler are you using?
descheduler version: v0.30.0
Does this issue reproduce with the latest release?
Yes.
Which descheduler CLI options are you using?
I'm using the helm chart v0.30.0
Please provide a copy of your descheduler policy config file
It's the default comming with the chart.
What k8s version are you using (
kubectl version
)?kubectl version
OutputWhat did you do?
I use the helm chart with the default options to deploy descheduler into my k8s cluster.
What did you expect to see?
Descheduler running successfully.
What did you see instead?
Descheduler throws config errors.
I will open a PR with my changes on the default profile.
The text was updated successfully, but these errors were encountered: