You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BUG-737502 added infrastructure to give the user the option to change… (#437)
* BUG-737502 added infrastructure to give the user teh option to change imagePullPolicy and made note of that in the README
* fixed readme, and added terratest
* added a new line to distinguish the new test
* reworded a part of the readme
Co-authored-by: locoe <[email protected]>
Co-authored-by: Davis Walsh <[email protected]>
Copy file name to clipboardExpand all lines: charts/pega/README.md
+6-1Lines changed: 6 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -759,14 +759,18 @@ The Helm charts also support an automated install or upgrade with a Kubernetes J
759
759
760
760
For installations of the Pega platform, you must specify the installer Docker image and an initial default password for the `[email protected]` user.
761
761
762
+
Along with this, you can configure the kubelet pull policy for the image. It is defaulted to `IfNotPresent`, meaning an image will be pulled if it is "not present". All possible options are `IfNotPresent`, `Always`, and `Never`. Always pulling an image ensures you always have the latest image at all times, even if the specific tag already exists on your machine.
763
+
762
764
Example:
763
765
764
766
```yaml
765
767
installer:
766
768
image: "YOUR_INSTALLER_IMAGE:TAG"
769
+
imagePullPolicy: "PREFERRED_IMAGE_PULL_POLICY"
767
770
adminPassword: "ADMIN_PASSWORD"
768
771
```
769
772
773
+
770
774
### Upgrades and patches
771
775
772
776
The Pega Helm charts support zero-downtime patch and upgrades processes which synchronize the required process steps to minimize downtime. With these zero-downtime processes, you and your customers can continue to access and use their applications in your environment with minimal disruption while you patch or upgrade your system.
@@ -782,7 +786,8 @@ Use the `installer` section of the values file with the appropriate parameters
782
786
Parameter | Description | Default value
783
787
--- | --- | ---
784
788
`image`| Reference the `platform/installer` Docker image that you downloaded and pushed to your Docker registry that your deployment can access. | `YOUR_INSTALLER_IMAGE:TAG`
785
-
`adminPassword`| Specify a temporary, initial password to log into teh Pega application. This will need to be changed at first login. The adminPassword value cannot start with "@". | `"ADMIN_PASSWORD"`
789
+
`imagePullPolicy`| Specify when to pull an image. | `IfNotPresent`
790
+
`adminPassword`| Specify a temporary, initial password to log into the Pega application. This will need to be changed at first login. The adminPassword value cannot start with "@". | `"ADMIN_PASSWORD"`
786
791
`upgrade.upgradeType:`|Specify the type of process, applying a patch or upgrading. | See the next table for details.
787
792
`upgrade.upgradeSteps:`|Specify the steps of a `custom` upgrade process that you want to complete. For `zero-downtime`, `out-of-place-rules`, `out-of-place-data`, or `in-place` upgrades, leave this parameter empty. | <ul>`enable_cluster_upgrade` `rules_migration` `rules_upgrade` `data_upgrade` `disable_cluster_upgrade`</ul>
788
793
`upgrade.targetRulesSchema:`|Specify the name of the schema you created the process creates for the new rules schema. | `""`
0 commit comments