-
Notifications
You must be signed in to change notification settings - Fork 208
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
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]>
- Loading branch information
1 parent
2d9f46b
commit 8d68d1c
Showing
3 changed files
with
53 additions
and
40 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 | |
|
||
For installations of the Pega platform, you must specify the installer Docker image and an initial default password for the `[email protected]` user. | ||
|
||
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. | ||
|
||
Example: | ||
|
||
```yaml | ||
installer: | ||
image: "YOUR_INSTALLER_IMAGE:TAG" | ||
imagePullPolicy: "PREFERRED_IMAGE_PULL_POLICY" | ||
adminPassword: "ADMIN_PASSWORD" | ||
``` | ||
|
||
|
||
### Upgrades and patches | ||
|
||
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 | |
Parameter | Description | Default value | ||
--- | --- | --- | ||
`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` | ||
`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"` | ||
`imagePullPolicy` | Specify when to pull an image. | `IfNotPresent` | ||
`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"` | ||
`upgrade.upgradeType:` |Specify the type of process, applying a patch or upgrading. | See the next table for details. | ||
`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> | ||
`upgrade.targetRulesSchema:` |Specify the name of the schema you created the process creates for the new rules schema. | `""` | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters