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

Merge pull request #338 from ingvagabund/filter-out-pods-by-namespaces

Browse Source 
Filter pods by namespaces
This commit is contained in:
Kubernetes Prow Robot
2020-07-28 08:57:47 -07:00
committed by GitHub
parent 4014ebad92 42db31683f
commit eee41ee111
16 changed files with 578 additions and 48 deletions
Download Patch File Download Diff File Expand all files Collapse all files

42
README.md
View File

@@ -234,6 +234,48 @@ strategies:
maxPodLifeTimeSeconds: 86400
````
## Namespace filtering
Strategies like `PodLifeTime`, `RemovePodsHavingTooManyRestarts`, `RemovePodsViolatingNodeTaints`,
`RemovePodsViolatingNodeAffinity` and `RemovePodsViolatingInterPodAntiAffinity` can specify `namespaces`
parameter which allows to specify a list of including, resp. excluding namespaces.
E.g.
```
apiVersion: "descheduler/v1alpha1"
kind: "DeschedulerPolicy"
strategies:
"PodLifeTime":
enabled: true
params:
maxPodLifeTimeSeconds: 86400
namespaces:
include:
- "namespace1"
- "namespace2"
```
In the examples `PodLifeTime` gets executed only over `namespace1` and `namespace2`.
The similar holds for `exclude` field:
```
apiVersion: "descheduler/v1alpha1"
kind: "DeschedulerPolicy"
strategies:
"PodLifeTime":
enabled: true
params:
maxPodLifeTimeSeconds: 86400
namespaces:
exclude:
- "namespace1"
- "namespace2"
```
The strategy gets executed over all namespaces but `namespace1` and `namespace2`.
It's not allowed to compute `include` with `exclude` field.
## Pod Evictions
When the descheduler decides to evict pods from a node, it employs the following general mechanism: