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

Implement major upgrade result annotations (#2727)

Browse Source 
Co-authored-by: Felix Kunde <felix-kunde@gmx.de>
Co-authored-by: Polina Bungina <27892524+hughcapet@users.noreply.github.com>
This commit is contained in:
Ida Novindasari
2024-08-28 15:26:12 +02:00
committed by GitHub
co-authored by Felix Kunde Polina Bungina
parent a09b7655c9
commit 2e398120d2
3 changed files with 135 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/administrator.md
+6
View File
@@ -85,6 +85,12 @@ It is also possible to define `maintenanceWindows` in the Postgres manifest to
better control when such automated upgrades should take place after increasing
the version.
### Upgrade annotations
When an upgrade is executed, the operator sets an annotation in the PostgreSQL resource, either `last-major-upgrade-success` if the upgrade succeeds, or `last-major-upgrade-failure` if it fails. The value of the annotation is a timestamp indicating when the upgrade occurred.
If a PostgreSQL resource contains a failure annotation, the operator will not attempt to retry the upgrade during a sync event. To remove the failure annotation, you can revert the PostgreSQL version back to the current version. This action will trigger the removal of the failure annotation.
## Non-default cluster domain
If your cluster uses a DNS domain other than the default `cluster.local`, this