securityContext bug

[chrisfort-sauce]

Steps to reproduce:

Uncomment the podSecurityContext and securityContext sections of the values.yaml and deploy.

Current behavior:

The values for runAsUser and runAsGroup are incorrectly placed in the resulting pods. They show up in the security context of the pod, instead of the container. fsGroup does not carry through at all.

Example:
spec:
containers:
securityContext: {}
securityContext:
runAsGroup: 101
runAsUser: 101

Expected behavior:

The pod scope securityContext should contain the fsGroup value. The container level scope should contain runAsUser and runAsGroup.

spec:
containers:
securityContext:
runAsGroup: 101
runAsUser: 101
securityContext:
fsGroup: 101