Documented serviceAccountName configuration for installer jobs

charts/pega/README.md

@@ -1182,6 +1182,17 @@ installer:
     label: value
 ```
 
+### Installer Service Account
+
+If the installer 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 jobs.
+
+Example:
+
+```yaml
+installer:
+  serviceAccountName: MY_INSTALLER_SERVICE_ACCOUNT_NAME
+```
+
 ### Mount the custom certificates into the Tomcat container
 
 Pega supports mounting and passing custom certificates into the tomcat container during your Pega Platform deployment. Pega supports the following certificate formats as long as they are encoded in base64: X.509 certificates such as PEM, DER, CER, CRT. To mount and pass the your custom certificates, use the `certificates` attributes as a map in the `values.yaml` file using the format in the following example.

charts/pega/charts/installer/values.yaml

@@ -34,6 +34,8 @@ bypassLoadEngineClasses: "false"
 bypassLoadAssembledClasses: "false"
 # If 'true', Helm will wait for the install or upgrade to finish, and only succeed if the job completes without error.
 waitForJobCompletion: "false"
+# Specify specific service account
+# serviceAccountName: MY_INSTALLER_SERVICE_ACCOUNT_NAME
 threads:
   # Maximum Idle Thread.Default is 5
   maxIdle: 5