Merge pull request #36062 from bergerhoffer/OSDOCS-2362

OSDOCS-2362: Adding new descheduler profiles and config

Author: bergerhoffer

modules/nodes-descheduler-configuring-profiles.adoc

@@ -34,14 +34,18 @@ spec:
   logLevel: Normal
   managementState: Managed
   operatorLogLevel: Normal
-  profiles:
-  - AffinityAndTaints       <1>
-  - TopologyAndDuplicates   <2>
-  - LifecycleAndUtilization <3>
+  profileCustomizations:
+    podLifetime: 48h        <1>
+  profiles:                 <2>
+  - AffinityAndTaints
+  - TopologyAndDuplicates   <3>
+  - LifecycleAndUtilization
+  - EvictPodsWithLocalStorage
+  - EvictPodsWithPVC
 ----
-<1> Enable the `AffinityAndTaints` profile, which evicts pods that violate inter-pod anti-affinity, node affinity, and node taints.
-<2> Enable the `TopologyAndDuplicates` profile, which evicts pods in an effort to evenly spread similar pods, or pods of the same topology domain, among nodes.
-<3> Enable the `LifecycleAndUtilization` profile, which evicts long-running pods and balances resource usage between nodes.
+<1> Optional: Enable a custom pod lifetime value for the `LifecycleAndUtilization` profile. Valid units are `ns`, `us`, `ms`, `s`, `m`, or `h`. The default pod lifetime is 24 hours.
+<2> Add one or more profiles to enable. Available profiles: `AffinityAndTaints`, `TopologyAndDuplicates`, `LifecycleAndUtilization`, `SoftTopologyAndDuplicates`, `EvictPodsWithLocalStorage`, and `EvictPodsWithPVC`.
+<3> Do not enable both `TopologyAndDuplicates` and `SoftTopologyAndDuplicates` because they will conflict with each other.
 +
 You can enable multiple profiles; the order that the profiles are specified in is not important.
 

modules/nodes-descheduler-installing.adoc

@@ -33,6 +33,7 @@ endif::[]
 . Create a descheduler instance.
 .. From the *Operators* -> *Installed Operators* page, click the *Kube Descheduler Operator*.
 .. Select the *Kube Descheduler* tab and click *Create KubeDescheduler*.
-.. Edit the settings as necessary and click *Create*.
+.. Edit the settings as necessary. You can configure the descheduler profiles and customizations now or after it has been created.
+.. Click *Create*.
 
 You can now configure the profiles for the descheduler. If you did not adjust the profiles when creating the descheduler instance from the web console, the `AffinityAndTaints` profile is enabled by default.

modules/nodes-descheduler-profiles.adoc

@@ -40,4 +40,15 @@ A node is considered overutilized if its usage is above 50% for any of the thres
 
 * `PodLifeTime`: evicts pods that are too old.
 +
-Pods that are older than 24 hours are removed.
+By default, pods that are older than 24 hours are removed. You can customize the pod lifetime value.
+
+`SoftTopologyAndDuplicates`:: This profile is the same as `TopologyAndDuplicates`, except that pods with soft topology constraints, such as `whenUnsatisfiable: ScheduleAnyway`, are also considered for eviction.
++
+[NOTE]
+====
+Do not enable both `SoftTopologyAndDuplicates` and `TopologyAndDuplicates` because they will conflict with each other.
+====
+
+`EvictPodsWithLocalStorage`:: This profile allows pods with local storage to be eligible for eviction.
+
+`EvictPodsWithPVC`:: This profile allows pods with persistent volume claims to be eligible for eviction.