kubernetes-sigs / descheduler

Descheduler for Kubernetes
https://sigs.k8s.io/descheduler
Apache License 2.0
4.5k stars 672 forks source link

Deprecate CronJob deployment approach #1340

Open knelasevero opened 10 months ago

knelasevero commented 10 months ago

This came up during community meeting of Jan 16 2024. Since there are some proposals to change descheduler to more of a controller than it is right now, with long running implications, maybe supporting the CronJob deployment approach isn't great for us in the future.

One of the reasons why folks use the CronJob approach is to have more control over which time the evictions are performed, as it happens here: https://github.com/kubernetes-sigs/descheduler/issues/1338

I remember getting questions from people asking the same thing (how to run it only at night). So before deprecating it might also be good to add a feature to better control intervals between loops with a cron like semantics.

pravarag commented 8 months ago

Hi @knelasevero , if this approach is being actively considered, I would like to contribute in any way possible. Kindly let me know :)

knelasevero commented 8 months ago

First step would be implementing a feature to better control intervals between loops with a cron like semantics I think we are very supportive of it.

k8s-triage-robot commented 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:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

ChandonPierre commented 4 months ago

Since there are some proposals to change descheduler to more of a controller than it is right now, with long running implications

Where can I read about these proposals?

I'm very interested in a descheduler controller - Instead of implementing my own, I'd rather work towards a proposed and agreed upon approach

Deltachaos commented 4 months ago

The downside of a single pod running as a controller is, that descheduler stops if the node where the descheduler runs is going down.

k8s-triage-robot commented 3 months ago

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:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

aslafy-z commented 3 months ago

/remove-lifecycle rotten

k8s-triage-robot commented 5 days 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:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale