podSecurityContext should be optional
Description
Not all clusters have the securitycontextdeny admission controller disabled by default, and having that option configured in the deployment with no possibility to turn it off is a blocker for such clusters, pods will just not be created.
Proposal
Include a variable securityDeny
or whatever other name to sorround the optional block
securityContext:
runAsUser: 100
fsGroup: 65533
Links to related issues and merge requests / references
None?