Documented serviceAccountName configuration for installer jobs (#847)

* Updated documentation * Fixed typo in addons * Addressed issues as per PR --------- Co-authored-by: Kishor Kumar Vasantala <[email protected]>
pegasystems · Jan 28, 2025 · 2bd32d6 · 2bd32d6
1 parent dfde0e3
commit 2bd32d6
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 0 deletions.
diff --git a/charts/pega/README.md b/charts/pega/README.md
@@ -1298,6 +1298,16 @@ installer:
     label: value
 ```
 
+### Installer Service Account
+If you require that the Pega installer job runs with a specific service account, you can specify a custom `serviceAccountName` for your job. For more information on service accounts, see [Configure Service Account](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/).
+
+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.

diff --git a/charts/pega/charts/installer/values.yaml b/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"
+# Optionally specify specific service account
+# serviceAccountName: MY_INSTALLER_SERVICE_ACCOUNT_NAME
 threads:
   # Maximum Idle Thread.Default is 5
   maxIdle: 5