From db1ef44627ea2d68caad0551595a7ce6938ac363 Mon Sep 17 00:00:00 2001 From: Julio Pasinatto Date: Mon, 5 Aug 2024 21:09:06 -0300 Subject: [PATCH] Update pg-db chart for 2.4.1 release --- charts/pg-db/Chart.yaml | 4 ++-- charts/pg-db/README.md | 10 +++++----- charts/pg-db/values.yaml | 10 +++++----- 3 files changed, 12 insertions(+), 12 deletions(-) diff --git a/charts/pg-db/Chart.yaml b/charts/pg-db/Chart.yaml index 2fe83f97..7cab1183 100644 --- a/charts/pg-db/Chart.yaml +++ b/charts/pg-db/Chart.yaml @@ -2,8 +2,8 @@ apiVersion: v2 name: pg-db description: 'A Helm chart to deploy the PostgreSQL database with the Percona Operator for PostgreSQL' type: application -version: 2.4.1 -appVersion: 2.4.0 +version: 2.4.2 +appVersion: 2.4.1 home: https://docs.percona.com/percona-operator-for-postgresql/2.0/ maintainers: - name: tplavcic diff --git a/charts/pg-db/README.md b/charts/pg-db/README.md index 522997f8..0a0f7c69 100644 --- a/charts/pg-db/README.md +++ b/charts/pg-db/README.md @@ -24,7 +24,7 @@ To install the chart with the `pg` release name using a dedicated namespace (rec ```sh helm repo add percona https://percona.github.io/percona-helm-charts/ -helm install my-db percona/pg-db --version 2.4.0 --namespace my-namespace +helm install my-db percona/pg-db --version 2.4.1 --namespace my-namespace ``` The chart can be customized using the following configurable parameters: @@ -32,9 +32,9 @@ The chart can be customized using the following configurable parameters: | Parameter | Description | Default | | ------------------------------- | ------------------------------------------------------------------------------|-------------------------------------------------------------| | `finalizers` | Finalizers list | `{}` | -| `crVersion` | CR Cluster Manifest version | `2.4.0` | +| `crVersion` | CR Cluster Manifest version | `2.4.1` | | `repository` | PostgreSQL container image repository | `percona/percona-postgresql-operator` | -| `image` | Postgres image | `percona/percona-postgresql-operator:2.4.0-ppg16.3-postgres` | +| `image` | Postgres image | `percona/percona-postgresql-operator:2.4.1-ppg16.3-postgres` | | `imagePullPolicy` | image Pull Policy | `Always` | | `port` | PostgreSQL port | `5432` | | `postgresVersion` | PostgreSQL container version tag | `16` | @@ -154,7 +154,7 @@ The chart can be customized using the following configurable parameters: | `backups.restore.enabled` | Enables or disables restoring a previously made backup | `false` | | `backups.restore.repoName` | Name of the pgBackRest repository that contains the backup to be restored | `repo1` | | `backups.restore.options` | The pgBackRest command-line options for the pgBackRest restore command | `--type=time` | -| `backups.pgbackrest.image` | Set this variable if you need to use a custom pgBackrest image | `percona/percona-postgresql-operator:2.4.0-ppg16.3-pgbackrest2.51-1` | +| `backups.pgbackrest.image` | Set this variable if you need to use a custom pgBackrest image | `percona/percona-postgresql-operator:2.4.1-ppg16.3-pgbackrest2.51-1` | | `backups.repos.repo2.s3.bucket` | Storage bucket | `` | | `backups.repos.repo2.s3.region` | S3-compatible storage name | `` | | `backups.repos.repo2.s3.endpoint` | S3-compatible storage endpoint | `` | @@ -177,7 +177,7 @@ The chart can be customized using the following configurable parameters: | `proxy.pgBouncer.customTLSSecret.name` | Custom external TLS secret name | `keycloakdb-pgbouncer.tls` | | `proxy.pgBouncer.securityContext` | The Kubernetes Pod security context for the pgBouncer instance | `{}` | | `proxy.pgBouncer.affinity.podAntiAffinity` | Pod anti-affinity, allows setting the standard Kubernetes affinity constraints of any complexity | `{}` | -| `proxy.pgBouncer.image` | Set this variable if you need to use a custom pgbouncer image | `percona/percona-postgresql-operator:2.4.0-ppg16.3-pgbouncer1.22.1` | +| `proxy.pgBouncer.image` | Set this variable if you need to use a custom pgbouncer image | `percona/percona-postgresql-operator:2.4.1-ppg16.3-pgbouncer1.22.1` | | `proxy.pgBouncer.replicas` | The number of pgbouncer instances | `3` | | `proxy.pgBouncer.resources.requests.cpu` | Container resource request for CPU | `1` | | `proxy.pgBouncer.resources.requests.memory` | Container resource request for RAM | `128Mi` | diff --git a/charts/pg-db/values.yaml b/charts/pg-db/values.yaml index 4659ebff..11dc2942 100644 --- a/charts/pg-db/values.yaml +++ b/charts/pg-db/values.yaml @@ -8,9 +8,9 @@ finalizers: # Set this if you want that operator deletes the ssl objects on cluster deletion # - percona.com/delete-ssl -crVersion: 2.4.0 +crVersion: 2.4.1 repository: percona/percona-postgresql-operator -image: percona/percona-postgresql-operator:2.4.0-ppg16.3-postgres +image: percona/percona-postgresql-operator:2.4.1-ppg16.3-postgres imagePullPolicy: Always postgresVersion: 16 # port: 5432 @@ -224,7 +224,7 @@ instances: proxy: pgBouncer: replicas: 3 - image: percona/percona-postgresql-operator:2.4.0-ppg16.3-pgbouncer1.22.1 + image: percona/percona-postgresql-operator:2.4.1-ppg16.3-pgbouncer1.22.1 # exposeSuperusers: true # resources: # limits: @@ -305,7 +305,7 @@ backups: pgbackrest: # metadata: # labels: - image: percona/percona-postgresql-operator:2.4.0-ppg16.3-pgbackrest2.51-1 + image: percona/percona-postgresql-operator:2.4.1-ppg16.3-pgbackrest2.51-1 # containers: # pgbackrest: # resources: @@ -481,7 +481,7 @@ pmm: # targetInstance: "" # extensions: -# image: percona/percona-postgresql-operator:2.4.0 +# image: percona/percona-postgresql-operator:2.4.1 # imagePullPolicy: Always # storage: # type: s3