-
Notifications
You must be signed in to change notification settings - Fork 1k
Comparing changes
Open a pull request
base repository: zalando/postgres-operator
base: v1.14.0
head repository: zalando/postgres-operator
compare: master
- 13 commits
- 68 files changed
- 4 contributors
Commits on Jan 3, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 4430aba - Browse repository at this point
Copy the full SHA 4430abaView commit details
Commits on Jan 7, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 46d5ebe - Browse repository at this point
Copy the full SHA 46d5ebeView commit details
Commits on Jan 15, 2025
-
Extend MaintenanceWindows parameter usage (#2810)
Consider maintenance window when migrating master pods and replacing pods (rolling update)
Configuration menu - View commit details
-
Copy full SHA for 8522331 - Browse repository at this point
Copy the full SHA 8522331View commit details
Commits on Jan 17, 2025
-
Only check maintenance window for upgrade after pg version recheck (#…
…2842) This way we avoid misleading "skipping major version upgrade, not in maintenance window" log line when c.currentMajorVersion is not initialized (==0)
Configuration menu - View commit details
-
Copy full SHA for e04b91d - Browse repository at this point
Copy the full SHA e04b91dView commit details
Commits on Jan 23, 2025
-
Partially revert #2810 (#2849)
Only schedule switchover for pod migration, consider mainWindow for PGVERSION env change
Configuration menu - View commit details
-
Copy full SHA for b0cfeb3 - Browse repository at this point
Copy the full SHA b0cfeb3View commit details
Commits on Jan 24, 2025
-
Configuration menu - View commit details
-
Copy full SHA for f49b4f1 - Browse repository at this point
Copy the full SHA f49b4f1View commit details
Commits on Jan 29, 2025
-
Critical operation PDB (#2830)
Create the second PDB to cover Pods with a special "critical operation" label set. This label is going to be assigned to all pg cluster's Pods by the Operator during a PG major version upgrade, by Patroni during a cluster/replica bootstrap. It can also be set manually or by any other automation tool.
Configuration menu - View commit details
-
Copy full SHA for a56ecaa - Browse repository at this point
Copy the full SHA a56ecaaView commit details
Commits on Jan 30, 2025
-
Protect Pods from disruptions during upgrades (#2844)
Co-authored-by: Felix Kunde <felix-kunde@gmx.de>
Configuration menu - View commit details
-
Copy full SHA for c8063eb - Browse repository at this point
Copy the full SHA c8063ebView commit details
Commits on Feb 14, 2025
-
fix creating secrets for rotation users (#2863)
* fix creating secrets for rotation users * rework annotation comparison on update to decide on when to call syncSecrets
Configuration menu - View commit details
-
Copy full SHA for 2a4be1c - Browse repository at this point
Copy the full SHA 2a4be1cView commit details
Commits on Feb 26, 2025
-
do not remove publications of slot defined in manifest (#2868)
* do not remove publications of slot defined in manifest * improve condition to sync streams * init publication tables map when adding manifest slots * need to update c.Stream when there is no update
Configuration menu - View commit details
-
Copy full SHA for 746df0d - Browse repository at this point
Copy the full SHA 746df0dView commit details
Commits on Mar 10, 2025
-
Configure (upcoming) Patroni bootstrap labels feature (#2872)
Set the value from the critical-operation-pdb's selector if PDBs are enabled
Configuration menu - View commit details
-
Copy full SHA for c7a586d - Browse repository at this point
Copy the full SHA c7a586dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 68c4b49 - Browse repository at this point
Copy the full SHA 68c4b49View commit details
Commits on May 20, 2025
-
Configuration menu - View commit details
-
Copy full SHA for ccb52c0 - Browse repository at this point
Copy the full SHA ccb52c0View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.14.0...master