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
Copy file name to clipboardExpand all lines: charts/pg-db/README.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ Useful links:
7
7
8
8
## Pre-requisites
9
9
*[Percona Operator for PostgreSQL](https://hub.helm.sh/charts/percona/pg-operator) running in your Kubernetes cluster. See installation details [here](https://github.com/percona/percona-helm-charts/tree/main/charts/pg-operator) or in the [Operator Documentation](https://www.percona.com/doc/kubernetes-operator-for-postgresql/helm.html).
10
-
* Kubernetes 1.28+
10
+
* Kubernetes 1.29+
11
11
* At least `v3.2.3` version of helm
12
12
13
13
# Installation
@@ -34,10 +34,10 @@ The chart can be customized using the following configurable parameters:
34
34
|`finalizers`| Finalizers list |`{}`|
35
35
|`crVersion`| CR Cluster Manifest version |`2.6.0`|
|`unmanaged`| Start cluster and don't manage it (cross cluster replication) |`false`|
43
43
|`standby.enabled`| Switch/start PostgreSQL Database in standby mode |`false`|
@@ -172,7 +172,7 @@ The chart can be customized using the following configurable parameters:
172
172
|`backups.restore.enabled`| Enables or disables restoring a previously made backup |`false`|
173
173
|`backups.restore.repoName`| Name of the pgBackRest repository that contains the backup to be restored |`repo1`|
174
174
|`backups.restore.options`| The pgBackRest command-line options for the pgBackRest restore command |`--type=time`|
175
-
|`backups.pgbackrest.image`| Set this variable if you need to use a custom pgBackrest image |`percona/percona-postgresql-operator:2.5.0-ppg16.4-pgbackrest2.53-1`|
175
+
|`backups.pgbackrest.image`| Set this variable if you need to use a custom pgBackrest image |`percona/percona-postgresql-operator:2.6.0-ppg17.2-pgbackrest2.54-0`|
@@ -196,7 +196,7 @@ The chart can be customized using the following configurable parameters:
196
196
|`proxy.pgBouncer.customTLSSecret.name`| Custom external TLS secret name |`keycloakdb-pgbouncer.tls`|
197
197
|`proxy.pgBouncer.securityContext`| The Kubernetes Pod security context for the pgBouncer instance |`{}`|
198
198
|`proxy.pgBouncer.affinity.podAntiAffinity`| Pod anti-affinity, allows setting the standard Kubernetes affinity constraints of any complexity |`{}`|
199
-
|`proxy.pgBouncer.image`| Set this variable if you need to use a custom pgbouncer image |`percona/percona-postgresql-operator:2.5.0-ppg16.4-pgbouncer1.23.1`|
199
+
|`proxy.pgBouncer.image`| Set this variable if you need to use a custom pgbouncer image |`percona/percona-postgresql-operator:2.6.0-ppg17.2-pgbouncer1.23.1`|
200
200
|`proxy.pgBouncer.replicas`| The number of pgbouncer instances |`3`|
201
201
|`proxy.pgBouncer.resources.requests.cpu`| Container resource request for CPU |`1`|
202
202
|`proxy.pgBouncer.resources.requests.memory`| Container resource request for RAM |`128Mi`|
@@ -209,7 +209,7 @@ The chart can be customized using the following configurable parameters:
209
209
||
210
210
|`pmm.enabled`| Enable integration with [Percona Monitoring and Management software](https://www.percona.com/blog/2020/07/23/using-percona-kubernetes-operators-with-percona-monitoring-and-management/)|`false`|
0 commit comments