-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
- Proposed title of this feature request
Fine Grained Configuration of LifecycleAndUtilization Profile.
2. What is the nature and description of the request?
Customer would like to be able to have fine grained control of the thresholds of the LifecycleAndUtilization descheudler profile. Specifically they would like to be able to specify the devLowNodeUtilizationThresholds field by providing integers instead only being able to select the values Low, Medium, and High.
Code reference for current Low, Medium, and High implementation: https://github.com/openshift/cluster-kube-descheduler-operator/blob/922decdd5807dd260dfb891847fae6af1373d2f0/pkg/operator/target_config_reconciler.go#L654-L662
3. Why does the customer need this? (List the business requirements here)
Customer would like to be able to deschedule pods from nodes experiencing high CPU or Memory utilization. Right now they need to periodically drain nodes when this happens which causes a high operational burden in their environment. The values provided by the Low, Medium, and High parameters do not meet their needs, so they would like to instead be able to fully customize the thresholds by specifying integers instead.
4. List any affected packages or components.
Descheduler and Descheduler Operator