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

remove AllowedMajorUpgradeVersions option

Browse Source
This commit is contained in:
Felix Kunde
2021-03-04 10:13:54 +01:00
parent 3d847b7b2b
commit 5a44ba1f45
13 changed files with 3 additions and 48 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/administrator.md
+2 -2
View File
@@ -32,8 +32,8 @@ In-place major version upgrades can be configured to be executed by the
operator with the `major_version_upgrade_mode` option. By default it is set
to `off` which means the cluster version will not change when increased in
the manifest. Still, a rolling update would be triggered updating the
`PGVERSION` variable. But `configure_spilo` will notice the version mismatch
and start the old version again.
`PGVERSION` variable. But Spilo's [`configure_spilo`](https://github.com/zalando/spilo/blob/master/postgres-appliance/scripts/configure_spilo.py)
script will notice the version mismatch and start the old version again.
In this scenario the major version could then be run by a user from within the
master pod. Exec into the container and run:
docs/reference/operator_parameters.md
-5
View File
@@ -193,11 +193,6 @@ CRD-configuration, they are grouped under the `major_version_upgrade` key.
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