Open runningman84 opened 1 month ago
What version of descheduler are you using?
descheduler version: 0.30.0
helm chart 0.30.0
Does this issue reproduce with the latest release?
yes
Which descheduler CLI options are you using?
just defaults
Please provide a copy of your descheduler policy config file
What k8s version are you using (kubectl version)?
kubectl version
$ kubectl version 1.30.1
What did you do?
Update to the latest version
What did you expect to see?
No errors
What did you see instead?
┌───────────────────────────────────────────────────────────── Logs(kube-system/descheduler-28615300-9npnf:descheduler)[tail] ─────────────────────────────────────────────────────────────┐ │ Autoscroll:On FullScreen:Off Timestamps:Off Wrap:On │ │ I0528 17:51:10.955100 1 secure_serving.go:57] Forcing use of http/1.1 only │ │ I0528 17:51:10.955537 1 named_certificates.go:53] "Loaded SNI cert" index=0 certName="self-signed loopback" certDetail="\"apiserver-loopback-client@1716918670\" [serving] validSe │ │ rvingFor=[apiserver-loopback-client] issuer=\"apiserver-loopback-client-ca@1716918669\" (2024-05-28 16:51:09 +0000 UTC to 2025-05-28 16:51:09 +0000 UTC (now=2024-05-28 17:51:10.9554702 │ │ 42 +0000 UTC))" │ │ I0528 17:51:10.955593 1 secure_serving.go:213] Serving securely on :10258 │ │ I0528 17:51:10.955613 1 tracing.go:87] Did not find a trace collector endpoint defined. Switching to NoopTraceProvider │ │ I0528 17:51:10.955710 1 tlsconfig.go:240] "Starting DynamicServingCertificateController" │ │ E0528 17:51:10.957580 1 server.go:96] "descheduler server" err="failed decoding descheduler's policy config \"/policy-dir/policy.yaml\": strict decoding error: unknown field \"no │ │ deAffinityType\"" │ │ E0528 17:51:10.957611 1 run.go:74] "command failed" err="failed decoding descheduler's policy config \"/policy-dir/policy.yaml\": strict decoding error: unknown field \"nodeAffin │ │ ityType\"" │ │ Stream closed EOF for kube-system/descheduler-28615300-9npnf (descheduler) │ │
seeing the same issue
stand-sure
commented
1 month ago stand-sure
commented
1 month ago
What version of descheduler are you using?
descheduler version: 0.30.0
helm chart 0.30.0
Does this issue reproduce with the latest release?
yes
Which descheduler CLI options are you using?
just defaults
Please provide a copy of your descheduler policy config file
just defaults
What k8s version are you using (
kubectl version)?kubectl versionOutputWhat did you do?
Update to the latest version
What did you expect to see?
No errors
What did you see instead?