@@ -65,7 +65,10 @@ the `PGVERSION` environment variable is set for the database pods. Since
6565In-place major version upgrades can be configured to be executed by the
6666operator with the ` major_version_upgrade_mode ` option. By default, it is
6767enabled (mode: ` manual ` ). In any case, altering the version in the manifest
68- will trigger a rolling update of pods to update the ` PGVERSION ` env variable.
68+ will update the desired ` PGVERSION ` . If ` maintenanceWindows ` are configured,
69+ major-version-related pod rotation is deferred until the next maintenance
70+ window. Without maintenance windows, the operator will trigger a rolling
71+ update of pods to apply the new ` PGVERSION ` .
6972Spilo's [ ` configure_spilo ` ] ( https://github.com/zalando/spilo/blob/master/postgres-appliance/scripts/configure_spilo.py )
7073script will notice the version mismatch but start the current version again.
7174
@@ -93,8 +96,9 @@ Thus, the `full` mode can create drift between desired and actual state.
9396### Upgrade during maintenance windows
9497
9598When ` maintenanceWindows ` are defined in the Postgres manifest the operator
96- will trigger a major version upgrade only during these periods. Make sure they
97- are at least twice as long as your configured ` resync_period ` to guarantee
99+ will trigger major-version-related pod rotation and the major version upgrade
100+ only during these periods. Make sure they are at least twice as long as your
101+ configured ` resync_period ` to guarantee
98102that operator actions can be triggered.
99103
100104### Upgrade annotations
0 commit comments