public_git/postgres-operator
1
0
Fork 0
mirror of https://github.com/zalando/postgres-operator.git synced 2026-10-05 05:35:37 +02:00
Code Issues Projects Releases Wiki Activity

reflect new major version upgrade options everywhere

Browse Source
This commit is contained in:
Felix Kunde
2021-02-26 12:28:24 +01:00
parent 217f306650
commit 90a166872d
16 changed files with 198 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/reference/operator_parameters.md
+28
View File
@@ -170,6 +170,34 @@ under the `users` key.
Postgres username used for replication between instances. The default is
`standby`.
## Major version upgrades
Parameters configuring automatic major version upgrades. In a
CRD-configuration, they are grouped under the `major_version_upgrade` key.
* **major_version_upgrade_mode**
Postgres Operator supports [in-place major version upgrade](../administrator.md#in-place-major-version-upgrade)
with three different modes:
`"off"` = no upgrade by the operator,
`"manual"` = manifest triggers action,
`"full"` = manifest and minimal version violation trigger upgrade.
Note, that with all three modes increasing the version in the manifest will
trigger a rolling update of the pods. The default is `"off"`.
* **minimal_major_version**
The minimal Postgres major version that will not automatically be upgraded
when `major_version_upgrade_mode` is set to `"full"`. The default is `"9.5"`.
* **target_major_version**
The target Postgres major version when upgrading clusters automatically
which violate the configured allowed `minimal_major_version` when
`major_version_upgrade_mode` is set to `"full"`. The default is `"13"`.
* **allowed_major_upgrade_versions**
Allow major version upgrades only to certain Postgres versions.
The default is `["12", "13"]`.
## Kubernetes resources
Parameters to configure cluster-related Kubernetes objects created by the