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

Single node clusters support #1347

Open
pablo-suazo opened this issue Feb 1, 2024 · 6 comments · May be fixed by #1350
Open

Single node clusters support #1347

pablo-suazo opened this issue Feb 1, 2024 · 6 comments · May be fixed by #1350
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@pablo-suazo
Copy link

I would like to use descheduler in a single node kubernetes cluster.

It is useful to me to automatically delete pods with too many restart or failed pods.

It is possible to overrride this check in any way?

if len(nodes) <= 1 { klog.V(1).InfoS("The cluster size is 0 or 1 meaning eviction causes service disruption or degradation. So aborting..") return fmt.Errorf("the cluster size is 0 or 1") }

@pablo-suazo pablo-suazo added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 1, 2024
@a7i
Copy link
Contributor

a7i commented Feb 11, 2024

/assign

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 11, 2024
@vaibhav2107
Copy link

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 8, 2024
@larryrensing
Copy link

any movement on this? it would be great to have!

@erikgb
Copy link

erikgb commented Sep 5, 2024

This issue becomes even more annoying when switching from cronjob to deployment workload. Since the rescheduled aborts, this makes the deployment pod crash-loop.

I suggest adding an option to enable support for single-node clusters. The default can still be to abort in single-node clusters to give users more awareness of the additional disturbance running descheduler with just a single cluster node.

@panteparak
Copy link

panteparak commented Oct 5, 2024

At work, I scale down replicas down to 1/2 on many of our apps during night times, which reduced down the number of nodes needed to 1 and cause the same error as above. It would be good if some sort of flag such as single node suppress such error

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

Successfully merging a pull request may close this issue.

8 participants