feat: Default to PG17 (#60)

paradedb · Dec 19, 2024 · ddafdfe · ddafdfe
1 parent f7d551f
commit ddafdfe
Show file tree

Hide file tree

Showing 34 changed files with 18 additions and 621 deletions.
diff --git a/README.md b/README.md
@@ -30,7 +30,7 @@ The [ParadeDB](https://github.com/paradedb/paradedb) Helm Chart is based on the
 
 Kubernetes, and specifically the CloudNativePG operator, is the recommended approach for deploying ParadeDB in production, with high availability. ParadeDB also provides a [Docker image](https://hub.docker.com/r/paradedb/paradedb) and [prebuilt binaries](https://github.com/paradedb/paradedb/releases) for Debian, Ubuntu and Red Hat Enterprise Linux.
 
-The ParadeDB Helm Chart supports Postgres 13+ and ships with Postgres 16 by default.
+The ParadeDB Helm Chart supports Postgres 13+ and ships with Postgres 17 by default.
 
 The chart is also available on [Artifact Hub](https://artifacthub.io/packages/helm/paradedb/paradedb).
 

diff --git a/charts/paradedb/Chart.yaml b/charts/paradedb/Chart.yaml
@@ -20,8 +20,8 @@ icon: https://raw.githubusercontent.com/paradedb/paradedb/main/docs/logo/light.s
 type: application
 
 # The Chart version, set in the publish CI workflow from GitHub Actions Variables
-# We default to v0.12.0 for testing and local development
-version: 0.12.0
+# We default to v0.12.1 for testing and local development
+version: 0.12.1
 
 sources:
   - https://github.com/paradedb/charts

diff --git a/charts/paradedb/README.md b/charts/paradedb/README.md
@@ -4,7 +4,7 @@ The [ParadeDB](https://github.com/paradedb/paradedb) Helm Chart is based on the
 
 Kubernetes, and specifically the CloudNativePG operator, is the recommended approach for deploying ParadeDB in production, with high availability. ParadeDB also provides a [Docker image](https://hub.docker.com/r/paradedb/paradedb) and [prebuilt binaries](https://github.com/paradedb/paradedb/releases) for Debian, Ubuntu and Red Hat Enterprise Linux.
 
-The ParadeDB Helm Chart supports Postgres 13+ and ships with Postgres 16 by default.
+The ParadeDB Helm Chart supports Postgres 13+ and ships with Postgres 17 by default.
 
 The chart is also available on [Artifact Hub](https://artifacthub.io/packages/helm/paradedb/paradedb).
 
@@ -309,8 +309,8 @@ refer to  the [CloudNativePG Documentation](https://cloudnative-pg.io/documentat
 | recovery.secret.create | bool | `true` | Whether to create a secret for the backup credentials |
 | recovery.secret.name | string | `""` | Name of the backup credentials secret |
 | type | string | `"paradedb"` | Type of the CNPG database. Available types: * `paradedb` * `paradedb-enterprise` |
-| version.paradedb | string | `"0.12.0"` | We default to v0.12.0 for testing and local development |
-| version.postgresql | string | `"16"` | PostgreSQL major version to use |
+| version.paradedb | string | `"0.12.1"` | We default to v0.12.1 for testing and local development |
+| version.postgresql | string | `"17"` | PostgreSQL major version to use |
 | poolers[].name | string | `` | Name of the pooler resource |
 | poolers[].instances | number | `1` | The number of replicas we want |
 | poolers[].type | [PoolerType][PoolerType] | `rw` | Type of service to forward traffic to. Default: `rw`. |

diff --git a/charts/paradedb/README.md.gotmpl b/charts/paradedb/README.md.gotmpl
@@ -4,7 +4,7 @@ The [ParadeDB](https://github.com/paradedb/paradedb) Helm Chart is based on the
 
 Kubernetes, and specifically the CloudNativePG operator, is the recommended approach for deploying ParadeDB in production, with high availability. ParadeDB also provides a [Docker image](https://hub.docker.com/r/paradedb/paradedb) and [prebuilt binaries](https://github.com/paradedb/paradedb/releases) for Debian, Ubuntu and Red Hat Enterprise Linux.
 
-The ParadeDB Helm Chart supports Postgres 13+ and ships with Postgres 16 by default.
+The ParadeDB Helm Chart supports Postgres 13+ and ships with Postgres 17 by default.
 
 The chart is also available on [Artifact Hub](https://artifacthub.io/packages/helm/paradedb/paradedb).
 

diff --git a/charts/paradedb/examples/basic.yaml b/charts/paradedb/examples/basic.yaml
@@ -1,7 +1,7 @@
 type: postgresql
 mode: standalone
 version:
-  postgresql: "16"
+  postgresql: "17"
 cluster:
   instances: 1
 backups:

diff --git a/charts/paradedb/examples/image-catalog-ref.yaml b/charts/paradedb/examples/image-catalog-ref.yaml
@@ -2,7 +2,7 @@ type: postgresql
 mode: standalone
 version:
   major: "16"
-  paradedb: "0.12.0"
+  paradedb: "0.12.1"
 cluster:
   instances: 1
   imageCatalogRef:

diff --git a/charts/paradedb/examples/image-catalog.yaml b/charts/paradedb/examples/image-catalog.yaml
@@ -1,14 +1,14 @@
 type: postgresql
 mode: standalone
 version:
-  major: "16"
-  paradedb: "0.12.0"
+  major: "17"
+  paradedb: "0.12.1"
 cluster:
   instances: 1
 backups:
   enabled: false
 imageCatalog:
   create: true
   images:
-    - major: 16
+    - major: 17
       image: my-custom-postgres-image:mytag
diff --git a/charts/paradedb/examples/paradedb.yaml b/charts/paradedb/examples/paradedb.yaml
@@ -1,8 +1,8 @@
 type: paradedb
 mode: standalone
 version:
-  postgresql: "16.3"
-  paradedb: "0.12.0"
+  postgresql: "17.0"
+  paradedb: "0.12.1"
 cluster:
   instances: 1
 backups:

diff --git a/charts/paradedb/test/postgresql-minio-backup-restore/00-minio_cleanup-assert.yaml b/charts/paradedb/test/postgresql-minio-backup-restore/00-minio_cleanup-assert.yaml
diff --git a/charts/paradedb/test/postgresql-minio-backup-restore/00-minio_cleanup.yaml b/charts/paradedb/test/postgresql-minio-backup-restore/00-minio_cleanup.yaml
diff --git a/charts/paradedb/test/postgresql-minio-backup-restore/01-standalone_cluster-assert.yaml b/charts/paradedb/test/postgresql-minio-backup-restore/01-standalone_cluster-assert.yaml
diff --git a/charts/paradedb/test/postgresql-minio-backup-restore/01-standalone_cluster.yaml b/charts/paradedb/test/postgresql-minio-backup-restore/01-standalone_cluster.yaml
diff --git a/charts/paradedb/test/postgresql-minio-backup-restore/02-data_write-assert.yaml b/charts/paradedb/test/postgresql-minio-backup-restore/02-data_write-assert.yaml
diff --git a/charts/paradedb/test/postgresql-minio-backup-restore/02-data_write.yaml b/charts/paradedb/test/postgresql-minio-backup-restore/02-data_write.yaml
diff --git a/charts/paradedb/test/postgresql-minio-backup-restore/03-backup.yaml b/charts/paradedb/test/postgresql-minio-backup-restore/03-backup.yaml
diff --git a/charts/paradedb/test/postgresql-minio-backup-restore/03-backup_completed-assert.yaml b/charts/paradedb/test/postgresql-minio-backup-restore/03-backup_completed-assert.yaml
diff --git a/charts/paradedb/test/postgresql-minio-backup-restore/03-backup_running-assert.yaml b/charts/paradedb/test/postgresql-minio-backup-restore/03-backup_running-assert.yaml
diff --git a/charts/paradedb/test/postgresql-minio-backup-restore/03-checkpoint.yaml b/charts/paradedb/test/postgresql-minio-backup-restore/03-checkpoint.yaml
diff --git a/charts/paradedb/test/postgresql-minio-backup-restore/04-post_backup_data_write-assert.yaml b/charts/paradedb/test/postgresql-minio-backup-restore/04-post_backup_data_write-assert.yaml
diff --git a/charts/paradedb/test/postgresql-minio-backup-restore/04-post_backup_data_write.yaml b/charts/paradedb/test/postgresql-minio-backup-restore/04-post_backup_data_write.yaml
diff --git a/charts/paradedb/test/postgresql-minio-backup-restore/05-recovery_backup_cluster-assert.yaml b/charts/paradedb/test/postgresql-minio-backup-restore/05-recovery_backup_cluster-assert.yaml
diff --git a/charts/paradedb/test/postgresql-minio-backup-restore/05-recovery_backup_cluster.yaml b/charts/paradedb/test/postgresql-minio-backup-restore/05-recovery_backup_cluster.yaml
diff --git a/charts/paradedb/test/postgresql-minio-backup-restore/06-data_test-assert.yaml b/charts/paradedb/test/postgresql-minio-backup-restore/06-data_test-assert.yaml
diff --git a/charts/paradedb/test/postgresql-minio-backup-restore/06-data_test.yaml b/charts/paradedb/test/postgresql-minio-backup-restore/06-data_test.yaml