Added support for custom envFrom

charts/pega/README.md

@@ -573,9 +573,9 @@ The `deploymentStrategy` can be used to optionally configure the [strategy](http
 
 ### Environment variables
 
-Pega supports a variety of configuration options for cluster-wide and application settings. In cases when you want to pass a specific environment variable into your deployment on a tier-by-tier basis, you specify a custom `env` block for your tier as shown in the example below.
+Pega supports a variety of configuration options for cluster-wide and application settings. In cases when you want to pass a specific environment variable into your deployment on a tier-by-tier basis, you specify a custom `env` or 'envFrom' block for your tier as shown in the example below.
 
-Example:
+Example 'env' block:
 
 ```yaml
 tier:
@@ -586,6 +586,18 @@ tier:
           value: MY_ENV_VALUE
 ```
 
+Example 'envFrom' block:
+
+```yaml
+tier:
+  - name: my-tier
+    custom:
+      envFrom:
+        - secretRef:
+            name: MY_SECRET_REF
+```
+
+
 ### Service Account
 
 If the pod needs to be run with a specific [service account](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/), you can specify a custom `serviceAccountName` for your deployment tier.

charts/pega/templates/_pega-deployment.tpl

@@ -207,6 +207,12 @@ spec:
         envFrom:
         - configMapRef:
             name: {{ template "pegaEnvironmentConfig" .root }}
+{{- if .custom }}
+{{- if .custom.envFrom }}
+        # Additional custom envFrom vars
+{{ toYaml .custom.envFrom | indent 8 }}
+{{- end }}
+{{- end }}
         resources:
           # Maximum CPU and Memory that the containers for {{ .name }} can use
           limits: