Closed evgkrsk closed 5 months ago
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".
Is your feature request related to a problem? Please describe. We use descheduler (thanks for it!) in our production clusters, but here is problem: to see effect of enabling new descheduling strategy without risk, you have to enable dry-run mode. But it is global (per-instance) switch, so you can't continue to apply already tested and fine-tuned strategy(es) and test new strategy safely.
Describe the solution you'd like Per-strategy option in policy definition to enable dry-run for current strategy only (disabled by default for backward compatibility).
Describe alternatives you've considered Many descheduler instances with different dry-run modes (on/off). Also, instances in dry-run mode have to disable leader election, in opposite to instances not in dry-run mode. Seems like resources and efforts waste for me.
What version of descheduler are you using?
descheduler version: latest at 16 Jun 2023.
Additional context It would be useful to add dry-run bool label in prometheus metrics to help with testing new strategies.