fix(kube-system): tune descheduler CPU request and eviction thresholds #167
No reviewers
Labels
No labels
area/bootstrap
area/ci
area/flux
area/kubernetes
area/media
area/observability
area/renovate
area/talos
community
hold
hold/upstream
priority/high
priority/low
priority/medium
renovate/container
renovate/forgejo-action
renovate/github-release
renovate/grafana-dashboard
renovate/helm
type/digest
type/major
type/minor
type/patch
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Exikle/Artemis-Cluster!167
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/descheduler-resources"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Lower CPU request 500m→100m to free scheduling headroom on cp-03 (was blocking rook-ceph-exporter/crashcollector from scheduling).
Adopt onedr0p LowNodeUtilization targetThresholds (75→50) for tighter node balancing.