You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<2> Optional: Set a list of user-created namespaces to include or exclude from descheduler operations. Use `excluded` to set a list of namespaces to exclude or use `included` to set a list of namespaces to include. Note that protected namespaces (`openshift-*`, `kube-system`, `hypershift`) are excluded by default.
61
63
<3> Optional: Enable a custom pod lifetime value for the `LifecycleAndUtilization` profile. Valid units are `s`, `m`, or `h`. The default pod lifetime is 24 hours.
62
64
<4> Optional: Specify a priority threshold to consider pods for eviction only if their priority is lower than the specified level. Use the `thresholdPriority` field to set a numerical priority threshold (for example, `10000`) or use the `thresholdPriorityClassName` field to specify a certain priority class name (for example, `my-priority-class-name`). If you specify a priority class name, it must already exist or the descheduler will throw an error. Do not set both `thresholdPriority` and `thresholdPriorityClassName`.
63
-
<5> Add one or more profiles to enable. Available profiles: `AffinityAndTaints`, `TopologyAndDuplicates`, `LifecycleAndUtilization`, `SoftTopologyAndDuplicates`, `EvictPodsWithLocalStorage`, and `EvictPodsWithPVC`.
64
-
<6> Do not enable both `TopologyAndDuplicates` and`SoftTopologyAndDuplicates`. Enabling both results in a conflict.
65
+
<5> Optional: Set the maximum number of pods to evict during each descheduler run.
66
+
<6> Add one or more profiles to enable. Available profiles: `AffinityAndTaints`, `TopologyAndDuplicates`, `LifecycleAndUtilization`,`SoftTopologyAndDuplicates`, `EvictPodsWithLocalStorage`, `EvictPodsWithPVC`, `CompactAndScale`, and `LongLifecycle`. Ensure that you do not enable profiles that conflict with each other.
65
67
66
68
You can enable multiple profiles; the order that the profiles are specified in is not important.
Copy file name to clipboardExpand all lines: modules/nodes-descheduler-profiles.adoc
+45-6Lines changed: 45 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -30,48 +30,87 @@ Pods with a node affinity type of `requiredDuringSchedulingIgnoredDuringExecutio
30
30
+
31
31
It enables the following strategies:
32
32
+
33
+
--
33
34
* `RemovePodsViolatingTopologySpreadConstraint`: finds unbalanced topology domains and tries to evict pods from larger ones when `DoNotSchedule` constraints are violated.
34
35
* `RemoveDuplicates`: ensures that there is only one pod associated with a replica set, replication controller, deployment, or job running on same node. If there are more, those duplicate pods are evicted for better pod distribution in a cluster.
36
+
--
37
+
+
38
+
[WARNING]
39
+
====
40
+
Do not enable `TopologyAndDuplicates` with any of the following profiles: `SoftTopologyAndDuplicates` or `CompactAndScale`. Enabling these profiles together results in a conflict.
41
+
====
35
42
36
43
`LifecycleAndUtilization`:: This profile evicts long-running pods and balances resource usage between nodes.
37
44
+
38
45
It enables the following strategies:
39
46
+
47
+
--
40
48
* `RemovePodsHavingTooManyRestarts`: removes pods whose containers have been restarted too many times.
41
49
+
42
50
Pods where the sum of restarts over all containers (including Init Containers) is more than 100.
43
51
44
52
* `LowNodeUtilization`: finds nodes that are underutilized and evicts pods, if possible, from overutilized nodes in the hope that recreation of evicted pods will be scheduled on these underutilized nodes.
53
+
54
+
** A node is considered underutilized if its usage is below 20% for all thresholds (CPU, memory, and number of pods).
55
+
56
+
** A node is considered overutilized if its usage is above 50% for any of the thresholds (CPU, memory, and number of pods).
57
+
45
58
+
46
-
A node is considered underutilized if its usage is below 20% for all thresholds (CPU, memory, and number of pods).
47
-
+
48
-
A node is considered overutilized if its usage is above 50% for any of the thresholds (CPU, memory, and number of pods).
59
+
Optionally, you can adjust these underutilized/overutilized threshold percentages by setting the Technology Preview field `devLowNodeUtilizationThresholds` to one the following values: `Low` for 10%/30%, `Medium` for 20%/50%, or `High` for 40%/70%. The default value is `Medium`.
49
60
50
61
* `PodLifeTime`: evicts pods that are too old.
51
62
+
52
63
By default, pods that are older than 24 hours are removed. You can customize the pod lifetime value.
64
+
--
65
+
+
66
+
[WARNING]
67
+
====
68
+
Do not enable `LifecycleAndUtilization` with any of the following profiles: `LongLifecycle` or `CompactAndScale`. Enabling these profiles together results in a conflict.
69
+
====
53
70
54
71
`SoftTopologyAndDuplicates`:: This profile is the same as `TopologyAndDuplicates`, except that pods with soft topology constraints, such as `whenUnsatisfiable: ScheduleAnyway`, are also considered for eviction.
55
72
+
56
-
[NOTE]
73
+
[WARNING]
57
74
====
58
75
Do not enable both `SoftTopologyAndDuplicates` and `TopologyAndDuplicates`. Enabling both results in a conflict.
59
76
====
60
77
61
78
`EvictPodsWithLocalStorage`:: This profile allows pods with local storage to be eligible for eviction.
62
79
63
80
`EvictPodsWithPVC`:: This profile allows pods with persistent volume claims to be eligible for eviction. If you are using `Kubernetes NFS Subdir External Provisioner`, you must add an excluded namespace for the namespace where the provisioner is installed.
81
+
82
+
`CompactAndScale`:: This profile enables the `HighNodeUtilization` strategy, which attempts to evict pods from underutilized nodes to allow a workload to run on a smaller set of nodes. A node is considered underutilized if its usage is below 20% for all thresholds (CPU, memory, and number of pods).
83
+
+
84
+
Optionally, you can adjust the underutilized percentage by setting the Technology Preview field `devHighNodeUtilizationThresholds` to one the following values: `Minimal` for 10%, `Modest` for 20%, or `Moderate` for 30%. The default value is `Modest`.
85
+
+
86
+
[WARNING]
87
+
====
88
+
Do not enable `CompactAndScale` with any of the following profiles: `LifecycleAndUtilization`, `LongLifecycle`, or `TopologyAndDuplicates`. Enabling these profiles together results in a conflict.
89
+
====
90
+
64
91
endif::nodes[]
65
92
ifdef::virt[]
66
93
Use the Technology Preview `DevPreviewLongLifecycle` profile to enable the descheduler on a virtual machine. This is the only descheduler profile currently available for {VirtProductName}. To ensure proper scheduling, create VMs with CPU and memory requests for the expected load.
94
+
endif::virt[]
67
95
68
-
`DevPreviewLongLifecycle`:: This profile balances resource usage between nodes and enables the following strategies:
96
+
// Show LongLifecycle profile both for virt and nodes
97
+
`LongLifecycle`:: This profile balances resource usage between nodes and enables the following strategies:
69
98
+
99
+
--
70
100
* `RemovePodsHavingTooManyRestarts`: removes pods whose containers have been restarted too many times and pods where the sum of restarts over all containers (including Init Containers) is more than 100. Restarting the VM guest operating system does not increase this count.
71
101
* `LowNodeUtilization`: evicts pods from overutilized nodes when there are any underutilized nodes. The destination node for the evicted pod will be determined by the scheduler.
72
102
** A node is considered underutilized if its usage is below 20% for all thresholds (CPU, memory, and number of pods).
73
103
** A node is considered overutilized if its usage is above 50% for any of the thresholds (CPU, memory, and number of pods).
74
-
endif::virt[]
104
+
--
105
+
+
106
+
--
107
+
ifdef::nodes[]
108
+
[WARNING]
109
+
====
110
+
Do not enable `LongLifecycle` with any of the following profiles: `LifecycleAndUtilization` or `CompactAndScale`. Enabling these profiles together results in a conflict.
Copy file name to clipboardExpand all lines: nodes/scheduling/descheduler/index.adoc
-3Lines changed: 0 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -8,9 +8,6 @@ toc::[]
8
8
9
9
While the xref:../../../nodes/scheduling/nodes-scheduler-about.adoc#nodes-scheduler-about[scheduler] is used to determine the most suitable node to host a new pod, the descheduler can be used to evict a running pod so that the pod can be rescheduled onto a more suitable node.
Copy file name to clipboardExpand all lines: nodes/scheduling/descheduler/nodes-descheduler-release-notes.adoc
+30-3Lines changed: 30 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,34 @@ The {descheduler-operator} allows you to evict pods so that they can be reschedu
10
10
11
11
These release notes track the development of the {descheduler-operator}.
12
12
13
-
:operator-name: The {descheduler-operator}
14
-
include::snippets/operator-not-available.adoc[]
15
-
16
13
For more information, see xref:../../../nodes/scheduling/descheduler/index.adoc#nodes-descheduler-about_nodes-descheduler-about[About the descheduler].
14
+
15
+
[id="descheduler-operator-release-notes-5.1.0"]
16
+
== Release notes for {descheduler-operator} 5.1.0
17
+
18
+
Issued: 23 October 2024
19
+
20
+
The following advisory is available for the {descheduler-operator} 5.1.0:
** `CompactAndScale`: This profile attempts to evict pods from underutilized nodes to allow a workload to run on a smaller set of nodes.
30
+
** `LongLifecycle`: This profile balances resource usage between nodes and enables the `RemovePodsHavingTooManyRestarts` and `LowNodeUtilization` strategies.
31
+
32
+
* For the `CompactAndScale` profile, you can use the Technology Preview field `devHighNodeUtilizationThresholds` to adjust the underutilized threshold value.
33
+
34
+
[id="descheduler-operator-5.1.0-bug-fixes"]
35
+
=== Bug fixes
36
+
37
+
* This release of the {descheduler-operator} addresses several Common Vulnerabilities and Exposures (CVEs).
0 commit comments