maw1146 commented 1 year ago

Hi, I'm not sure if this is a bug or I'm doing something wrong.

In the HelmRelease values, I setup different strategies and applied the param to exclude namespaces, however it still tries to evict pods in these namespaces.

Here couple of examples: ` RemovePodsViolatingTopologySpreadConstraint: enabled: true params: namespaces: exclude:

"istio-system"
"vsphere-csi" includeSoftConstraints: false LowNodeUtilization: enabled: true params: namespaces: exclude:
"istio-system"

"vsphere-csi" nodeResourceUtilizationThresholds: thresholds:

cpu: 15

        # memory: 20
        # pods: 10
        cpu: 30
        memory: 40
        pods: 25
      targetThresholds:
        cpu: 45
        memory: 50
        pods: 30`

maw1146 commented 1 year ago

Here maybe is better: RemovePodsViolatingTopologySpreadConstraint: enabled: true params: namespaces: exclude:

"istio-system"
"vsphere-csi" includeSoftConstraints: false LowNodeUtilization: enabled: true params: namespaces: exclude:
"istio-system"
"vsphere-csi" nodeResourceUtilizationThresholds: thresholds: cpu: 30 memory: 40 pods: 25 targetThresholds: cpu: 45 memory: 50 pods: 30

damemi commented 1 year ago

@maw1146 could you provide the whole descheduler config? You can also wrap it in 3 backticks (```) for multiline code to preserve indentation

k8s-triage-robot commented 7 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

dvdmuckle commented 7 months ago

I feel this may be similar to an issue my team is currently running into, except with namespaces.include. I can paste our helm config here, or I can open up a new issue.

damemi commented 7 months ago

@dvdmuckle sure, feel free to post your config here. If you have descheduler logs too, that would also help

k8s-triage-robot commented 6 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 5 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue with /reopen
Mark this issue as fresh with /remove-lifecycle rotten
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 5 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/descheduler/issues/1185#issuecomment-2041495825): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

kubernetes-sigs / descheduler

Strategy - Exclude Namespaces #1185

cpu: 15