ISSUE-711: add support for securityContext to SRS

charts/backingservices/charts/srs/templates/srsservice_deployment.yaml

@@ -105,6 +105,10 @@ spec:
               value: ""
           resources:
             {{- toYaml .Values.srsRuntime.resources | nindent 12 }}
+          securityContext:
+            {{- toYaml .Values.srsRuntime.securityContext | nindent 12 }}
+      securityContext:
+        {{- toYaml .Values.securityContext | nindent 8 }}
       {{- if .Values.srsStorage.tls.enabled }}
       volumes:
       - name: srs-certificates

charts/backingservices/values.yaml

@@ -32,12 +32,24 @@ srs:
     # Specify secret names as an array of comma-separated strings. For example: ["secret1", "secret2"]
     imagePullSecretNames: []
 
+    # Container securityContext
+    # securityContext:
+    #   runAsUser: 9999 # app
+    #   allowPrivilegeEscalation: false
+    #   capabilities:
+    #     drop:
+    #     - all
+
     env:
       # AuthEnabled may be set to true when there is an authentication mechanism in place between SRS and Pega Infinity.
       AuthEnabled: false
       # When `AuthEnabled` is `true`, enter the appropriate public key URL. When `AuthEnabled` is `false`(default), leave this parameter empty.
       OAuthPublicKeyURL: ""
 
+  # Pod securityContext
+  # securityContext:
+  #   runAsUser: 9999 # app
+
   # This section specifies the elasticsearch cluster configuration.
   srsStorage:
     # Setting srsStorage.provisionInternalESCluster to true will provision an internal elasticsearch cluster using the configuration