kubernetes-sigs /descheduler

Descheduler for Kubernetes

★ 5,577⑂ 815👁 46⑃ 1,226● 717▤ 79
GoApache-2.0Created 2017-07-28sigs.k8s.io/descheduler
下载:descheduler-helm-chart-0.37.0descheduler-helm-chart-0.37.0 ↓0.37.02026-10-04
+1
日增长
5,577
stars
815
forks
46
watchers
1,226
prs
717
issues
79
releases

README

!Release Charts


	↗️️ Click at the [bullet list icon] at the top right corner of the Readme visualization for the github generated table of contents.



    


 Descheduler for Kubernetes

Scheduling in Kubernetes is the process of binding pending pods to nodes, and is performed by
a component of Kubernetes called kube-scheduler. The scheduler's decisions, whether or where a
pod can or can not be scheduled, are guided by its configurable policy which comprises of set of
rules, called predicates and priorities. The scheduler's decisions are influenced by its view of
a Kubernetes cluster at that point of time when a new pod appears for scheduling.
As Kubernetes clusters are very dynamic and their state changes over time, there may be desire
to move already running pods to some other nodes for various reasons:

 Some nodes are under or over utilized.
 The original scheduling decision does not hold true any more, as taints or labels are added to
or removed from nodes, pod/node affinity requirements are not satisfied any more.
 Some nodes failed and their pods moved to other nodes.
 New nodes are added to clusters.

Consequently, there might be several pods scheduled on less desired nodes in a cluster.
Descheduler, based on its policy, finds pods that can be moved and evicts them. Please
note, in current implementation, descheduler does not schedule replacement of evicted pods
but relies on the default scheduler for that.

 ⚠️  Documentation Versions by Release

If you are using a published release of Descheduler (such as
registry.k8s.io/descheduler/descheduler:v0.37.0), follow the documentation in
that version's release branch, as listed below:

|Descheduler Version|Docs link|
|---|---|
|v0.37.x|release-1.37|
|v0.36.x|release-1.36|
|v0.35.x|release-1.35|
|v0.34.x|release-1.34|
|v0.33.x|release-1.33|
|v0.32.x|release-1.32|
|v0.31.x|release-1.31|
|v0.30.x|release-1.30|

The
master
branch is considered in-development and the information presented in it may not
work for previous versions.

 Quick Start

The descheduler can be run as a Job, CronJob, or Deployment inside of a k8s cluster. It has the
advantage of being able to be run multiple times without needing user intervention.
The descheduler pod is run as a critical pod in the kube-system namespace to avoid
being evicted by itself or by the kubelet.

 Run As A Job


kubectl create -f kubernetes/base/rbac.yaml
kubectl create -f kubernetes/base/configmap.yaml
kubectl create -f kubernetes/job/job.yaml


 Run As A CronJob


kubectl create -f kubernetes/base/rbac.yaml
kubectl create -f kubernetes/base/configmap.yaml
kubectl create -f kubernetes/cronjob/cronjob.yaml


 Run As A Deployment


kubectl create -f kubernetes/base/rbac.yaml
kubectl create -f kubernetes/base/configmap.yaml
kubectl create -f kubernetes/deployment/deployment.yaml


 Install Using Helm

Starting with release v0.18.0 there is an official helm chart that can be used to install the
descheduler. See the helm chart README for detailed in

Top issues

Latest release

descheduler-helm-chart-0.37.0 descheduler-helm-chart-0.37.0 2026-10-04
Descheduler for Kubernetes is used to rebalance clusters by evicting pods that can potentially be scheduled on better nodes. In the current implementation, descheduler does not schedule replacement of evicted pods but relies on the default scheduler for that.

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON