unknown field nodeAffinityType error with v0.30.0

[headyj]

What version of descheduler are you using?

descheduler version: v0.30.0

Does this issue reproduce with the latest release?

Actually It only occurs with latest release

Which descheduler CLI options are you using?

default command sent by the cronjob: https://github.com/kubernetes-sigs/descheduler/blob/master/charts/descheduler/templates/cronjob.yaml#L79-L89

Please provide a copy of your descheduler policy config file

default policy

What k8s version are you using (kubectl version)?

v1.29 (EKS)

What did you do?

Running the cronjob is not working since v0.30.0 with almost default chart values:

fullnameOverride: descheduler
cronJobApiVersion: batch/v1
schedule: "10 3 * * *"
suspend: false

What did you expect to see?

The job should be executed without error

What did you see instead?

It returns the following error:

descheduler-28615870-wl9vc E0529 03:20:38.162660       1 run.go:74] "command failed" err="failed decoding descheduler's policy config \"/policy-dir/policy.yaml\": strict decoding error: unknown field \"nodeAffinityType\""

[vytautaskelmelissislt]

Revert to v0.29.0 and everything will work like in charms.

[a7i]

I believe this was addressed in this PR: #1412

I will work on cutting a patch release v0.30.1

[a7i]

Meanwhile you can try specifying your own policy as highlighted here

[a7i]

#1425

[a7i]

v0.30.1 is out, let me know how it goes.

I tested and verified default profile works ✔️

[headyj]

Thank you @a7i , I tested v0.30.1 and the cronjob is working now!

[a7i]

thank you for reporting this!

/close

[k8s-ci-robot]

@a7i: Closing this issue.

In response to this:

thank you for reporting this!

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.