Closed mstefany closed 6 months ago
Hi @mstefany Thank you for all the details!
However, I am unable to reproduce this issue. Is it possible that you have multiple profiles defined in the policy?
I also meet the same sitution as @mstefany
Hi @mstefany Thank you for all the details!
However, I am unable to reproduce this issue. Is it possible that you have multiple profiles defined in the policy?
Nope, there shouldn't be anything additional except what I posted. No multiple profiles, etc. One thing however - I think I don't use the "default" profile name.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
What version of descheduler are you using?
descheduler version: v0.27.1
Does this issue reproduce with the latest release?
Yes.
Which descheduler CLI options are you using?
Helm Chart defaults:
args
Please provide a copy of your descheduler policy config file
policy
ConfigMap
What k8s version are you using (
kubectl version
)?kubectl version
OutputWhat did you do?
Provided the ConfigMap with policy above, descheduler fails to start:
Logs show problem with
priorityThreshold
:There is no
priorityThreshold.value
specified in the policy/ConfigMap
, yet it argues that only one can be specified. If I remove thename
key and replace it withvalue
with some reasonable value, descheduler successfully starts:What did you expect to see?
Running descheduler pod.
What did you see instead?
descheduler failing to start with error show above.