Mike Dame
Mike Dame
Yeah, `descheduler_pods_evicted` is meant as an aggregated count of the total pods evicted. So right now it would show an overall value like ``` descheduler_pods_evicted{...} 123 ``` or since it's...
See also: https://prometheus.io/docs/practices/naming/#labels > CAUTION: Remember that every unique combination of key-value label pairs represents a new time series, which can dramatically increase the amount of data stored. Do not...
@mczimm thanks, yes I understand what you are asking for. See my comment above, where following the Prometheus docs this is probably not a good idea given the high cardinality...
ping @spike-liu, are you able to check [`find_dirs_containing_comment_tags`](https://github.com/kubernetes-sigs/descheduler/blob/2b1746cda8883c199329510ac021b1c6badf4984/hack/lib/generator-help.sh#L15) to see if there is an issue there? It looks like the generator is giving some weird output in https://github.com/kubernetes-sigs/descheduler/pull/976#issuecomment-1272207052 as well
@spike-liu thanks for debugging this! yes, if you wouldn't mind opening a PR with your fixes it would be really helpful
/cc @knelasevero
> Perhaps I'm misunderstanding something but I thought the docs specify that descheduler will never deschedule a single pod? @rouke-broersma could you share which part of the docs makes it...
We chose not to allow namespace filtering for NodeUtilization because it ultimately only hinders the strategy (see https://github.com/kubernetes-sigs/descheduler/issues/391 for a longer discussion on it) tl;dr is that NodeUtilization is designed...
> So, for NodeUtilization all namespaces need to be considered for balancing, and here in this PR we are only deciding not to evict a pod from an excluded namespace...