Deprecate node-selector, max-pods-to-evict-per-node and evict-local-storage-pods flags and promote then to policy v1alpha1 fields#380
Conversation
41e7a2e to
5f64dc0
Compare
4ad4d63 to
cc49e2e
Compare
damemi
left a comment
There was a problem hiding this comment.
/approve
think this looks good to me. pretty simple change and the flags are still supported though clearly marked as deprecated 👍
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: damemi, ingvagabund The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@ingvagabund please update the output from |
…torage-pods flags and promote then to policy v1alpha1 fields
cc49e2e to
89541f7
Compare
|
@seanmalloy |
|
/lgtm |
|
@ingvagabund I think you can remove the hold when you are ready for merge. Thanks! |
|
/hold cancel |
…gs-under-descheduler-polic Deprecate node-selector, max-pods-to-evict-per-node and evict-local-storage-pods flags and promote then to policy v1alpha1 fields
…er/release-4.21/registry.access.redhat.com-ubi9-ubi-minimal-latest chore(deps): update registry.access.redhat.com/ubi9/ubi-minimal:latest docker digest to 90bd85d - abandoned
--node-selectorpromoted tonodeSelector--evict-local-storage-podspromoted toevictLocalStoragePods--max-pods-to-evict-per-nodepromoted tomaxNoOfPodsToEvictPerNodeConfiguration in the descheduler policy takes preference over the flags
Keeping
descheduling-intervalflag as it is since it's not related to a particular strategy but to the overall controller configuration.