Add support to define (overwrite) of securityContext or pod security context

[cbugneac-nex]

What this PR does / why we need it: Add support to define (overwrite) SecurityContext for containers & pod security context.

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged): Fixes #1437

Special notes for your reviewer:

Link helm chart:

$ helm lint ./
==> Linting ./

1 chart(s) linted, 0 chart(s) failed

TODOs:

• [ ] squashed commits
• [x] includes documentation
• [ ] adds unit tests

[k8s-ci-robot]

Welcome @cbugneac-nex!

It looks like this is your first PR to kubernetes-sigs/secrets-store-csi-driver 🎉. 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-sigs/secrets-store-csi-driver 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. :smiley:

[k8s-ci-robot]

Hi @cbugneac-nex. 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/test-infra repository.

[cbugneac-nex]

/kind feature

[cbugneac-nex]

Hi @aramase @nilekhc please could you review this PR ?

[cbugneac-nex]

Hi @aramase @nilekhc @ritazh @tam7t please could you review this PR when you have time ?

[cbugneac-nex]

Hi @aramase please could you review it once again ?

[cbugneac-nex]

Hi @aramase @nilekhc @ritazh @tam7t please could you review this PR when you have time ?

[linux-foundation-easycla[bot]]

The committers listed above are authorized under a signed CLA.

• :white_check_mark: login: Constantin07 / name: Constantin Bugneac (813d013e237a57e3d1820d006166cd2ba30dc345, 18c78fb83938ccae6f3a109a1dcfb4def8117ad9)
• :white_check_mark: login: cbugneac-nex / name: Constantin Bugneac (d00ff30ea22cea94c71ea105b74cbe2fa8caaf09, 5852ec4e5dfb5af6bbe18694896ebfadbea53519, 4e68d06f2f76d464eae197167ad3b85b78ba6e59)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: cbugneac-nex Once this PR has been reviewed and has the lgtm label, please ask for approval from aramase. 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]

PR needs rebase.

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-triage-robot]

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale

[k8s-triage-robot]

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle rotten

[aramase]

Closing this due to inactivity. Please reopen the PR after the comments are addressed.

/close

[k8s-ci-robot]

@aramase: Closed this PR.

In response to this:

Closing this due to inactivity. Please reopen the PR after the comments are addressed.

/close

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.