Add sysctl exemptions to controller PSP

[towolf]

What this PR does / why we need it:

I would like to be able to support this construction in my DaemonSet, I have control over the host and this is the easiest way to bump the socket properties.

securityContext:
  sysctls:
    - name: net.core.somaxconn
      value: "8192"

Since the PSP needs to whitelist this specific sysctl I'd like to be able to prvoide a map of sysctls, and not merge this into the securityContext.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Which issue/s this PR fixes

How Has This Been Tested?

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have added tests to cover my changes.
• All new and existing tests passed.

[k8s-ci-robot]

Hi @towolf. Thanks for your PR.

I'm waiting for a kubernetes 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.

[k8s-ci-robot]

Welcome @towolf!

It looks like this is your first PR to kubernetes/ingress-nginx 🎉. 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/ingress-nginx 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. 😃

[ChiefAlexander]

/ok-to-test
/assign @ChiefAlexander

[ChiefAlexander]

You will need to bump the chart version before we are able to get this in.

[towolf]

@ChiefAlexander bumped version only in Chart.yml, is that sufficient?

Do I also have to replace the version in the Makefile, in the docs, Changelog, etc? re-generate the files under ./deploy/static/?

[ChiefAlexander]

bumped version only in Chart.yml, is that sufficient?

Yup, that is all you need todo. The generation of the files under static is done on release.

[ChiefAlexander]

/lgtm

[ChiefAlexander]

Thanks for the PR!

[ChiefAlexander]

/lgtm cancel

[ChiefAlexander]

Sorry, one extra thing @towolf
Please Squash your commits down. https://github.com/kubernetes/community/blob/master/contributors/guide/pull-requests.md#6-squashing

[towolf]

@ChiefAlexander sure, done.

[towolf]

/assign @ChiefAlexander

[k8s-ci-robot]

@towolf: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
pull-ingress-nginx-test-lua	836d370d93d570f6b47847f5e0d4a34534dc1814	link	/test pull-ingress-nginx-test-lua
pull-ingress-nginx-lualint	836d370d93d570f6b47847f5e0d4a34534dc1814	link	/test pull-ingress-nginx-lualint
pull-ingress-nginx-test	219ed09a557a71dc0ba21f3d181d5582363ed340	link	/test pull-ingress-nginx-test
pull-ingress-nginx-e2e-1-15	219ed09a557a71dc0ba21f3d181d5582363ed340	link	/test pull-ingress-nginx-e2e-1-15
pull-ingress-nginx-e2e-1-17	219ed09a557a71dc0ba21f3d181d5582363ed340	link	/test pull-ingress-nginx-e2e-1-17
pull-ingress-nginx-golint	219ed09a557a71dc0ba21f3d181d5582363ed340	link	/test pull-ingress-nginx-golint
pull-ingress-nginx-e2e-1-16	219ed09a557a71dc0ba21f3d181d5582363ed340	link	/test pull-ingress-nginx-e2e-1-16
pull-ingress-nginx-e2e-1-18	219ed09a557a71dc0ba21f3d181d5582363ed340	link	/test pull-ingress-nginx-e2e-1-18
pull-ingress-nginx-gofmt	219ed09a557a71dc0ba21f3d181d5582363ed340	link	/test pull-ingress-nginx-gofmt

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.

[ChiefAlexander]

/lgtm
Thanks!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ChiefAlexander, towolf

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:

• charts/ingress-nginx/OWNERS [ChiefAlexander]

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