You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* add validation for PG resources and volume size
* check resource requests also on UPDATE and SYNC + update docs
* if cluster was running don't error on sync
## Use taints and tolerations for dedicated PostgreSQL nodes
186
215
187
216
To ensure Postgres pods are running on nodes without any other application pods,
@@ -305,7 +334,7 @@ Things to note:
305
334
- There is no way to transform a non-standby cluster to a standby cluster
306
335
through the operator. Adding the standby section to the manifest of a running
307
336
Postgres cluster will have no effect. However, it can be done through Patroni
308
-
by adding the [standby_cluster](https://github.com/zalando/patroni/blob/bd2c54581abb42a7d3a3da551edf0b8732eefd27/docs/replica_bootstrap.rst#standby-cluster)
337
+
by adding the [standby_cluster](https://github.com/zalando/patroni/blob/bd2c54581abb42a7d3a3da551edf0b8732eefd27/docs/replica_bootstrap.rst#standby-cluster)
309
338
section using `patronictl edit-config`. Note that the transformed standby
310
339
cluster will not be doing any streaming. It will be in standby mode and allow
311
340
read-only transactions only.
@@ -384,7 +413,7 @@ specified but globally disabled in the configuration. The
384
413
385
414
## Increase volume size
386
415
387
-
PostgreSQL operator supports statefulset volume resize if you're using the
416
+
Postgres operator supports statefulset volume resize if you're using the
388
417
operator on top of AWS. For that you need to change the size field of the
389
418
volume description in the cluster manifest and apply the change:
0 commit comments