Sok3t/descheduler
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/descheduler.git synced 2026-01-26 05:14:13 +01:00
Code Packages Releases Activity

Merge pull request #1379 from yuanchen8911/readme

Browse Source 
Fix and improve the namespace filtering description in README
This commit is contained in:
Kubernetes Prow Robot
2024-04-18 17:55:45 -07:00
committed by GitHub
parent 2c06a33d41 10d0ce0dfa
commit b95380641f
1 changed files with 5 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@@ -743,7 +743,7 @@ profiles:
### Namespace filtering ### Namespace filtering
The following strategies accept a `namespaces` parameter which allows to specify a list of including, resp. excluding namespaces: The following strategies accept a `namespaces` parameter which allows to specify a list of including and excluding namespaces respectively:
* `PodLifeTime` * `PodLifeTime`
* `RemovePodsHavingTooManyRestarts` * `RemovePodsHavingTooManyRestarts`
* `RemovePodsViolatingNodeTaints` * `RemovePodsViolatingNodeTaints`
@@ -753,11 +753,10 @@ The following strategies accept a `namespaces` parameter which allows to specify
* `RemovePodsViolatingTopologySpreadConstraint` * `RemovePodsViolatingTopologySpreadConstraint`
* `RemoveFailedPods` * `RemoveFailedPods`
The following strategies accept an `evictableNamespaces` parameter which allows to specify a list of excluding namespaces:
The following strategies accept a `evictableNamespaces` parameter which allows to specify a list of excluding namespaces:
* `LowNodeUtilization` and `HighNodeUtilization` (Only filtered right before eviction) * `LowNodeUtilization` and `HighNodeUtilization` (Only filtered right before eviction)
For example with PodLifeTime: In the following example with `PodLifeTime`, `PodLifeTime` gets executed only over `namespace1` and `namespace2`.
```yaml ```yaml
apiVersion: "descheduler/v1alpha2" apiVersion: "descheduler/v1alpha2"
@@ -778,8 +777,7 @@ profiles:
- "PodLifeTime" - "PodLifeTime"
``` ```
In the example `PodLifeTime` gets executed only over `namespace1` and `namespace2`. The similar holds for `exclude` field. The strategy gets executed over all namespaces but `namespace1` and `namespace2` in the following example.
The similar holds for `exclude` field:
```yaml ```yaml
apiVersion: "descheduler/v1alpha2" apiVersion: "descheduler/v1alpha2"
@@ -800,9 +798,7 @@ profiles:
- "PodLifeTime" - "PodLifeTime"
``` ```
The strategy gets executed over all namespaces but `namespace1` and `namespace2`. It's not allowed to combine `include` with `exclude` field.
It's not allowed to compute `include` with `exclude` field.
### Priority filtering ### Priority filtering