Enable customization of securityContext for containers

[andrewmyhre]

Describe the solution you'd like
The webhook containers currently require privilege escalation to execute. In our organization Kubernetes clusters strictly enforce security context to disallow privilege escalation without sufficient justification. We have been maintaining our own fork of this Helm chart with the following amendment to the upgrade webhook job manifests:

spec:
  template:
    spec:
        containers:
        - name: crds-upgrade # same for crds-keep
          securityContext:
            allowPrivilegeEscalation: false

The webhooks are able to operate without privilege escalation enabled. We don't want to maintain our own fork of the Helm chart, we would prefer that the securityContext for these containers is able to be configured via the values.yaml file.

Anything else you would like to add:

Environment:

• Secrets Store CSI Driver version: (use the image tag): v1.4.6
• Kubernetes version: (use kubectl version):

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale