Allow securityContext.Privileged to be configurable

[KapilSareen]

Fixes #15628

Proposed Changes

• Added support for configuring the Privileged field in securityContext.
  • The Privileged field can now be explicitly set to false by the user.
  • Default behavior (when unset) remains unchanged as nil.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: KapilSareen / name: Kapil Sareen (4809dca, 55e26ad)

[knative-prow]

Welcome @KapilSareen! It looks like this is your first PR to knative/serving 🎉

[knative-prow]

Hi @KapilSareen. Thanks for your PR.

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

[knative-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: KapilSareen
Once this PR has been reviewed and has the lgtm label, please assign salaboy 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
• pkg/apis/OWNERS

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

[KapilSareen]

Hi @skonto, I’ve addressed the reviews on my end. Let me know if there’s anything else needed.

[skonto]

/ok-to-test