You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`metricsProviders`|`[]object`|`nil`| Enables various metrics providers like Kubernetes [Metrics Server](https://kubernetes-sigs.github.io/metrics-server/)|
The Default Evictor Plugin is used by default for filtering pods before processing them in an strategy plugin, or for applying a PreEvictionFilter of pods before eviction. You can also create your own Evictor Plugin or use the Default one provided by Descheduler. Other uses for the Evictor plugin can be to sort, filter, validate or group pods by different criteria, and that's why this is handled by a plugin and not configured in the top level config.
@@ -163,8 +174,9 @@ maxNoOfPodsToEvictPerNode: 5000 # you don't need to set this, unlimited if not s
163
174
maxNoOfPodsToEvictPerNamespace: 5000# you don't need to set this, unlimited if not set
164
175
maxNoOfPodsToEvictTotal: 5000# you don't need to set this, unlimited if not set
165
176
gracePeriodSeconds: 60# you don't need to set this, 0 if not set
166
-
metricsCollector:
167
-
enabled: true # you don't need to set this, metrics are not collected if not set
177
+
# you don't need to set this, Kubernetes metrics are not collected if not set
178
+
metricsProviders:
179
+
- source: KubernetesMetrics
168
180
profiles:
169
181
- name: ProfileName
170
182
pluginConfig:
@@ -288,9 +300,10 @@ A resource consumption above (resp. below) this window is considered as overutil
288
300
This approach is chosen in order to maintain consistency with the kube-scheduler, which follows the same
289
301
design for scheduling pods onto nodes. This means that resource usage as reported by Kubelet (or commands
290
302
like `kubectl top`) may differ from the calculated consumption, due to these components reporting
291
-
actual usage metrics. Metrics-based descheduling can be enabled by setting `metricsUtilization.metricsServer` field.
292
-
In order to have the plugin consume the metrics the metric collector needs to be configured as well.
293
-
See `metricsCollector` field at [Top Level configuration](#top-level-configuration) for available options.
303
+
actual usage metrics. Metrics-based descheduling can be enabled by setting `metricsUtilization.metricsServer` field (deprecated)
304
+
or `metricsUtilization.source` field to `KubernetesMetrics`.
305
+
In order to have the plugin consume the metrics the metric provider needs to be configured as well.
306
+
See `metricsProviders` field at [Top Level configuration](#top-level-configuration) for available options.
294
307
295
308
**Parameters:**
296
309
@@ -303,7 +316,8 @@ See `metricsCollector` field at [Top Level configuration](#top-level-configurati
0 commit comments