Enable bounded CPU rebalancing after successful dry runs
This commit is contained in:
1 parent
5923b7c455
commit
5d7c5f4392
2 files changed
+3
-2
No files matched your search
@@ -22,3 +22,6 @@ sync. Existing running Jobs must finish before suspension takes full effect.
|
||||
Review after changes to workload mix; do not remove PVC and infrastructure
|
||||
protections to force a more even CPU graph. CPU requests determine whether a
|
||||
replacement can fit even when observed utilization is low.
|
||||
|
||||
Live evictions enabled on 2026-11-01 after successful dry-run cycles.
|
||||
The review selected replicated dashboard/ingress pods and respected the caps.
|
||||
@@ -10,9 +10,7 @@ resources:
|
||||
limits:
|
||||
cpu: null
|
||||
memory: 256Mi
|
||||
# Observe the first cycle before enabling evictions.
|
||||
cmdOptions:
|
||||
dry-run: true
|
||||
v: 3
|
||||
deschedulerPolicy:
|
||||
maxNoOfPodsToEvictPerNode: 1
|
||||
|
||||
Reference in new issue
Block a user