charts: add missing permission for policy

[linuxmaniac]

fixes #1595

missing permission

I0103 10:56:41.502794       1 reflector.go:376] Caches populated for *v1.PriorityClass from k8s.io/client-go/informers/factory.go:160
W0103 10:56:41.504105       1 reflector.go:569] k8s.io/client-go/informers/factory.go:160: failed to list *v1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User "system:serviceaccount:kube-system:descheduler" cannot list resource "poddisruptionbudgets" in API group "policy" at the cluster scope
E0103 10:56:41.504128       1 reflector.go:166] "Unhandled Error" err="k8s.io/client-go/informers/factory.go:160: Failed to watch *v1.PodDisruptionBudget: failed to list *v1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User \"system:serviceaccount:kube-system:descheduler\" cannot list resource \"poddisruptionbudgets\" in API group \"policy\" at the cluster scope" logger="UnhandledError"

[linux-foundation-easycla]

• ✅login: linuxmaniac / (5a201a3)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

Welcome @linuxmaniac!

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. 😃

[k8s-ci-robot]

Hi @linuxmaniac. 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-sigs/prow repository.

[linuxmaniac]

@a7i maybe you can take a look at this one too. Thanks

[a7i]

/ok-to-test

[a7i]

/retest-required

[linuxmaniac]

/retest-required

[a7i]

/lgtm
/approve

Thank you @linuxmaniac for your contribution 🏆

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: a7i

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [a7i]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[a7i]

/retest-required

[googs1025]

can we cherry pick this commit. this seem to be fix
@a7i @linuxmaniac 🤔