feat: add securityContext at podlevel #325
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Due to a Kyverno policy, I would like to be able to set the securityContext at podlevel for all Kyverno pods. The chart currently only offers the possibility to set the securityContext at container level. This causes my Kyverno policy to fail only for the
policy-reporter-kyverno-plugin-<random-string>
pod.Solution
I can optionally set the securityContext to podlevel with these incoming changes.