Skip to content
New issue

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

Latest version does not work with helm chart anymore #1418

Open
runningman84 opened this issue May 28, 2024 · 1 comment
Open

Latest version does not work with helm chart anymore #1418

runningman84 opened this issue May 28, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@runningman84
Copy link

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 version Output
$ 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)                                                                                                               │
│                                                                           
@runningman84 runningman84 added the kind/bug Categorizes issue or PR as related to a bug. label May 28, 2024
@stand-sure
Copy link

seeing the same issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants