descheduler
descheduler copied to clipboard
kubernetes-sigs
Add error output for namespace filters
Related to: https://github.com/kubernetes-sigs/descheduler/issues/970
- Added log information for pods skipping eviction due to namespace filtering (include or exclude).
- Added unittests
As mentioned in the #970 issue, there are at least a couple of ways to achieve this but changing the the ListPodsOnANode seemed too much as it would require more extensive changes. The benefit of the approach I took is that all pods are shown in the logs which makes it easier to troubleshoot any missed pods due to filtering or other configs.
Please let me know if further changes are required. :+1:
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign a7i for approval by writing /assign @a7i in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Welcome @migueleliasweb!
It looks like this is your first PR to kubernetes-sigs/descheduler 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.
You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.
You can also check if kubernetes-sigs/descheduler has its own contribution guidelines.
You may want to refer to our testing guide if you run into trouble with your tests not passing.
If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!
Thank you, and welcome to Kubernetes. :smiley:
Hi @migueleliasweb. Thanks for your PR.
I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@migueleliasweb: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| pull-descheduler-verify-master | 2d60281087718fa0e5112f07c695b0ae4dcb8a30 | link | true | /test pull-descheduler-verify-master |
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
$ ./hack/update-generated-deep-copies.sh
$ git status
On branch output-errors-for-namespace-filters
Untracked files:
(use "git add <file>..." to include in what will be committed)
k8s.io/
sigs.k8s.io/
Running the script the output says to run creates these folders but I wasn't expecting the change to be this big. Did I do something wrong?
$ git status -u
On branch output-errors-for-namespace-filters
Untracked files:
(use "git add <file>..." to include in what will be committed)
k8s.io/api/admission/v1/zz_generated.deepcopy.go
k8s.io/api/admission/v1beta1/zz_generated.deepcopy.go
k8s.io/api/admissionregistration/v1/zz_generated.deepcopy.go
k8s.io/api/admissionregistration/v1beta1/zz_generated.deepcopy.go
k8s.io/api/apiserverinternal/v1alpha1/zz_generated.deepcopy.go
k8s.io/api/apps/v1/zz_generated.deepcopy.go
k8s.io/api/apps/v1beta1/zz_generated.deepcopy.go
k8s.io/api/apps/v1beta2/zz_generated.deepcopy.go
k8s.io/api/authentication/v1/zz_generated.deepcopy.go
k8s.io/api/authentication/v1beta1/zz_generated.deepcopy.go
k8s.io/api/authorization/v1/zz_generated.deepcopy.go
k8s.io/api/authorization/v1beta1/zz_generated.deepcopy.go
k8s.io/api/autoscaling/v1/zz_generated.deepcopy.go
k8s.io/api/autoscaling/v2/zz_generated.deepcopy.go
k8s.io/api/autoscaling/v2beta1/zz_generated.deepcopy.go
....
# the list goes on for a total of 90 files created, not changed (which is what I was expecting)
@migueleliasweb: PR needs rebase.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
@migueleliasweb: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| pull-descheduler-verify-master | 2d60281087718fa0e5112f07c695b0ae4dcb8a30 | link | true | /test pull-descheduler-verify-master |
| pull-descheduler-test-e2e-k8s-master-1-26 | 2d60281087718fa0e5112f07c695b0ae4dcb8a30 | link | true | /test pull-descheduler-test-e2e-k8s-master-1-26 |
| pull-descheduler-test-e2e-k8s-master-1-27 | 2d60281087718fa0e5112f07c695b0ae4dcb8a30 | link | true | /test pull-descheduler-test-e2e-k8s-master-1-27 |
| pull-descheduler-test-e2e-k8s-master-1-28 | 2d60281087718fa0e5112f07c695b0ae4dcb8a30 | link | true | /test pull-descheduler-test-e2e-k8s-master-1-28 |
| pull-descheduler-test-e2e-k8s-master-1-29 | 2d60281087718fa0e5112f07c695b0ae4dcb8a30 | link | true | /test pull-descheduler-test-e2e-k8s-master-1-29 |
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle rotten - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Reopen this PR with
/reopen - Mark this PR as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closed this PR.
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closedYou can:
- Reopen this PR with
/reopen- Mark this PR as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.