charts/descheduler: add PodSecurityPolicy support

[invidian]

This commit adds restrictive PodSecurityPolicy, which can be
optionally created, so descheduler can be deployed on clusters with
PodSecurityPolicy admission controller, but which do not ship default
policies.

Signed-off-by: Mateusz Gozdek mgozdekof@gmail.com

[k8s-ci-robot]

Welcome @invidian!

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 @invidian. 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.

[damemi]

/ok-to-test

[invidian]

level=error msg="Timeout exceeded: try increasing it by passing --timeout option"

Seems linter timeout should be increased?

[damemi]

level=error msg="Timeout exceeded: try increasing it by passing --timeout option"

Seems linter timeout should be increased?

That's a weird error, and it's coming from the golang linter, so let's try a retest first maybe just an infra issue
/retest

[damemi]

/approve
looks good to me, though I wonder if we should also provide this somehow for non-helm deployments (under our /kubernetes manifests)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: damemi, invidian

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 [damemi]

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

[seanmalloy]

/assign

[seanmalloy]

@invidian sorry for the delay on the review. Thanks for submitting the pull request!

I think the helm chart configuration section should also be updated as part of this PR.

[seanmalloy]

/lgtm