Fix incorrectly placed fsGroup annotation in the Helm chart

This appears to be a pod-wide option according to the k8s API docs, so
placing it in the container's securityContext results in deploy errors.

Signed-off-by: Ryan Gonzalez <[email protected]>

Author: refi64

chart/values.yaml

@@ -24,8 +24,8 @@ fullnameOverride: ""
 
 podAnnotations: {}
 
-podSecurityContext: {}
-  # fsGroup: 2000
+podSecurityContext:
+  fsGroup: 1001
 
 securityContext:
   capabilities:
@@ -34,7 +34,6 @@ securityContext:
   readOnlyRootFilesystem: true
   runAsNonRoot: true
   allowPrivilegeEscalation: false
-  fsGroup: 1001
   runAsUser: 1001
   runAsGroup: 1001