helm chart: apply least required privileges in security contexts

[rptaylor]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Remove unneeded/unused privileges, to follow security best practices by default and enable installation of kueue on clusters that enforce PSS.

Which issue(s) this PR fixes:

Fixes #3850

Special notes for your reviewer:

Users can keep the same behaviour as before if they want by setting

controllerManager:
  manager:
    podSecurityContext:
      runAsNonRoot: true
      seccompProfile: null
    containerSecurityContext:
      allowPrivilegeEscalation: false
      capabilities: null

Does this PR introduce a user-facing change?

NONE

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rptaylor
Once this PR has been reviewed and has the lgtm label, please assign mimowo 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

[k8s-ci-robot]

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

[netlify]

✅ Deploy Preview for kubernetes-sigs-kueue ready!

Name	Link
🔨 Latest commit	7d9a450
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-kueue/deploys/6778494afcdba3000809c02e
😎 Deploy Preview	https://deploy-preview-3925--kubernetes-sigs-kueue.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[kannon92]

/ok-to-test

Should we add this as the default deployment for the manager pod of kueue in the kustomize?

[rptaylor]

Should we add this as the default deployment for the manager pod of kueue in the kustomize?

Probably the different deployment options should be as consistent as possible with each other.

[kannon92]

Probably the different deployment options should be as consistent as possible with each other.

Yea, I'd add this here

[mimowo]

Is this change required? If no please revert / move to a dedicated PR.

[rptaylor]

Yes, an updated chart always needs an updated version, unless perhaps you have some CI that automatically takes care of incrementing the chart version? But the comment right there says "This version number should be incremented each time you make changes to the chart and its templates".

[mimowo]

Please also update the manager.yaml.