Drop NET_BIND_SERVICE for port binding

[jkroepke]

What this PR does / why we need it:

See #10002 .

Kubernetes 1.22 consider net.ipv4.ip_unprivileged_port_start as safe sysctl. This allows us to bind applications like ingress-nginx on port < 1024 without using the NET_BIND_SERVICE capability. This may resolve some issue issues around debugging capability and using the sysctl may a clean alternative.

Looking to the support matrix, Kubernetes 1.23 is the minimum supported version which fits the Kubernetes minimum requirements.

The sysctl net.ipv4.ip_unprivileged_port_start is compatible with PSA baseline and restricted.

make image implements a toggle for setting capabilities on that image. make image SETCAP=true would result into an image with capabilities as it known.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• CVE Report (Scanner found CVE and adding report)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation only

Which issue/s this PR fixes

fixes #10002

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 unit and/or e2e tests to cover my changes.
• All new and existing tests passed.

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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]

Hi @jkroepke. 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.

[jkroepke]

This PR might be a bit too aggressive, since It contains a breaking changes. An alternative solution would be:

• pushing a separate image with an suffix like -nocap
• having the ingress-nginx. dump-init and nginx binary twice inside the image. On binary set have the capabilities while the other have the suffix -nocap without any capabilities.

The ingess-nginx helm chart would handle this with an additional toggle.

[netlify]

❌ Deploy Preview for kubernetes-ingress-nginx failed.

Name	Link
🔨 Latest commit	ac20c1f
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-ingress-nginx/deploys/6499eea7e7d0b3000893ae3e

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jkroepke
Once this PR has been reviewed and has the lgtm label, please assign tao12345666333 for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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