Merge pull request #2 from CrunchyData/main

update

Author: ianibo

helm/install/Chart.yaml

@@ -4,5 +4,5 @@ description: Installer for PGO, the open source Postgres Operator from Crunchy D
 
 type: application
 # The version below should match the version on the PostgresCluster CRD
-version: 5.3.0
-appVersion: 5.3.0
+version: 5.3.1
+appVersion: 5.3.1

helm/install/crds/postgres-operator.crunchydata.com_pgupgrades.yaml

@@ -6,7 +6,7 @@ metadata:
   creationTimestamp: null
   labels:
     app.kubernetes.io/name: pgo
-    app.kubernetes.io/version: 5.3.0
+    app.kubernetes.io/version: 5.3.1
   name: pgupgrades.postgres-operator.crunchydata.com
 spec:
   group: postgres-operator.crunchydata.com

helm/install/crds/postgres-operator.crunchydata.com_postgresclusters.yaml

@@ -6,7 +6,7 @@ metadata:
   creationTimestamp: null
   labels:
     app.kubernetes.io/name: pgo
-    app.kubernetes.io/version: 5.3.0
+    app.kubernetes.io/version: 5.3.1
   name: postgresclusters.postgres-operator.crunchydata.com
 spec:
   group: postgres-operator.crunchydata.com

helm/install/values.yaml

@@ -1,39 +1,33 @@
 ---
 # controllerImages are used to run the PostgresCluster and PGUpgrade controllers.
 controllerImages:
-  cluster: registry.developers.crunchydata.com/crunchydata/postgres-operator:ubi8-5.3.0-0
-  upgrade: registry.developers.crunchydata.com/crunchydata/postgres-operator-upgrade:ubi8-5.3.0-0
+  cluster: registry.developers.crunchydata.com/crunchydata/postgres-operator:ubi8-5.3.1-0
+  upgrade: registry.developers.crunchydata.com/crunchydata/postgres-operator-upgrade:ubi8-5.3.1-0
 
 # relatedImages are used when an image is omitted from PostgresCluster or PGUpgrade specs.
 relatedImages:
   postgres_15:
-    image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-15.1-0
+    image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-15.2-0
   postgres_15_gis_3.3:
-    image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres-gis:ubi8-15.1-3.3-0
+    image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres-gis:ubi8-15.2-3.3-0
   postgres_14:
-    image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-14.6-2
+    image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-14.7-0
   postgres_14_gis_3.1:
-    image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres-gis:ubi8-14.6-3.1-2
+    image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres-gis:ubi8-14.7-3.1-0
   postgres_14_gis_3.2:
-    image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres-gis:ubi8-14.6-3.2-2
+    image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres-gis:ubi8-14.7-3.2-0
   postgres_14_gis_3.3:
-    image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres-gis:ubi8-14.6-3.3-2
-  postgres_13:
-    image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-13.9-2
-  postgres_13_gis_3.0:
-    image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres-gis:ubi8-13.9-3.0-2
-  postgres_13_gis_3.1:
-    image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres-gis:ubi8-13.9-3.1-2
+    image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres-gis:ubi8-14.7-3.3-0
   pgadmin:
-    image: registry.developers.crunchydata.com/crunchydata/crunchy-pgadmin4:ubi8-4.30-8
+    image: registry.developers.crunchydata.com/crunchydata/crunchy-pgadmin4:ubi8-4.30-10
   pgbackrest:
-    image: registry.developers.crunchydata.com/crunchydata/crunchy-pgbackrest:ubi8-2.41-2
+    image: registry.developers.crunchydata.com/crunchydata/crunchy-pgbackrest:ubi8-2.41-4
   pgbouncer:
-    image: registry.developers.crunchydata.com/crunchydata/crunchy-pgbouncer:ubi8-1.17-5
+    image: registry.developers.crunchydata.com/crunchydata/crunchy-pgbouncer:ubi8-1.18-0
   pgexporter:
-    image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres-exporter:ubi8-5.3.0-0
+    image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres-exporter:ubi8-5.3.1-0
   pgupgrade:
-    image: registry.developers.crunchydata.com/crunchydata/crunchy-upgrade:ubi8-5.3.0-0
+    image: registry.developers.crunchydata.com/crunchydata/crunchy-upgrade:ubi8-5.3.1-0
 
 # singleNamespace controls where PGO watches for PostgresClusters. When false,
 # PGO watches for and responds to PostgresClusters in all namespaces. When true,

helm/postgres/Chart.yaml

@@ -3,5 +3,5 @@ name: postgrescluster
 description: A Helm chart for Kubernetes
 type: application
 # The version below should match the version on the PostgresCluster CRD
-version: 5.3.0
-appVersion: 5.3.0
+version: 5.3.1
+appVersion: 5.3.1

helm/postgres/templates/_s3.tpl

@@ -7,6 +7,9 @@ repo{{ add .index 1 }}-s3-key={{ .s3.key }}
   {{- end }}
   {{- if .s3.keySecret }}
 repo{{ add .index 1 }}-s3-key-secret={{ .s3.keySecret }}
+  {{- end }}
+  {{- if .s3.keyType }}
+repo{{ add .index 1 }}-s3-key-type={{ .s3.keyType }}
   {{- end }}
   {{- if .s3.encryptionPassphrase }}
 repo{{ add .index 1 }}-cipher-pass={{ .s3.encryptionPassphrase }}

helm/postgres/templates/postgres.yaml

@@ -191,7 +191,9 @@ spec:
   {{- if .Values.standby }}
   standby:
     enabled: {{ .Values.standby.enabled }}
-    repoName: {{ required "repoName must be set when enabling standby mode." .Values.standby.repoName }}
+    repoName: {{ .Values.standby.repoName }}
+    host: {{ .Values.standby.host }}
+    port: {{ .Values.standby.port }}
   {{- end }}
   {{- if .Values.supplementalGroups }}
   supplementalGroups:

helm/postgres/values.yaml

@@ -15,9 +15,9 @@
 # available as one of the "RELATED_IMAGE_POSTGRES_..." images as part of the PGO
 # installation if you want to deploy the image without setting the "postgres"
 # image variable. This value is required.
-postgresVersion: 14
+postgresVersion: 15
 
-# postGISVersion if sets and coupled with a PostGIS enabled container, enables
+# postGISVersion if set and coupled with a PostGIS enabled container, enables
 # PostGIS. This version number needs to be available as one of the
 # "RELATED_IMAGE_POSTGRES_..." images as part of the PGO installation if you
 # want to deploy the image without setting the "postgres" image variable.
@@ -35,7 +35,7 @@ postgresVersion: 14
 # pgBouncerReplicas: 1
 
 # monitoring enables the ability to monitor the Postgres cluster through a
-# metrics exporter than can be scraped by Prometheus. This defaults to the value
+# metrics exporter that can be scraped by Prometheus. This defaults to the value
 # below.
 # monitoring: false
 
@@ -47,19 +47,19 @@ postgresVersion: 14
 # below value. "postgresVersion" needs to match the version of Postgres that is
 # used here. If using the GIS-enabled Postgres image, you need to ensure
 # "postGISVersion" matches the version of PostGIS used.
-# imagePostgres: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-13.8-1
+# imagePostgres: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-15.2-0
 
 # imagePgBackRest is the pgBackRest backup utility image. This defaults to the
 # below value.
-# imagePgBackRest: registry.developers.crunchydata.com/crunchydata/crunchy-pgbackrest:ubi8-2.41-2
+# imagePgBackRest: registry.developers.crunchydata.com/crunchydata/crunchy-pgbackrest:ubi8-2.41-4
 
 # imagePgBouncer is the image for the PgBouncer connection pooler. This defaults
 # to the below value.
-# imagePgBouncer: registry.developers.crunchydata.com/crunchydata/crunchy-pgbouncer:ubi8-1.17-5
+# imagePgBouncer: registry.developers.crunchydata.com/crunchydata/crunchy-pgbouncer:ubi8-1.18-0
 
 # imageExporter is the image name for the exporter used as a part of monitoring.
 # This defaults to the value below.
-# imageExporter: registry.developers.crunchydata.com/crunchydata/crunchy-postgres-exporter:ubi8-5.3.0-0
+# imageExporter: registry.developers.crunchydata.com/crunchydata/crunchy-postgres-exporter:ubi8-5.3.1-0
 
 ###########################
 # Basic Postgres Settings #
@@ -133,7 +133,7 @@ postgresVersion: 14
 # patroni: {}
 
 # users sets any custom Postgres users and databases that they have  access to
-# as well as any permissions assoicated with the user account.
+# as well as any permissions associated with the user account.
 # users: {}
 
 # dataSource specifies a data source for bootstrapping a Postgres cluster.
@@ -149,21 +149,23 @@ postgresVersion: 14
 # provides the information for the replication user.
 # customReplicationTLSSecret: {}
 
-# databaseInitSQL referencs a ConfigMap that contains a SQL file that should be
+# databaseInitSQL references a ConfigMap that contains a SQL file that should be
 # run a cluster bootstrap.
 # databaseInitSQL:
 #   name: bootstrap-sql
 #   key: bootstrap.sql
 
-# standby sets whether or not to run this as a standby cluster. Both of the
-# values below are required to enable a standby cluster. Setting "enabled" to
-# "true" eunables the standby cluster while "repoName" points to a pgBackRest
-# archive to replay WAL files from.
+# standby sets whether to run this as a standby cluster. Setting "enabled" to
+# "true" enables the standby cluster while "repoName" points to a pgBackRest
+# archive to replay WAL files from, and "host" and "port" point to a primary
+# cluster from which to stream data.
 # standby:
 #   enabled: false
 #   repoName: repo1
+#   host: "192.0.2.2"
+#   port: 5432
 
-# shutdown when set scales the entire workload to zero. By default this is not
+# shutdown when set scales the entire workload to zero. By default, this is not
 # set.
 # shutdown: true
 
@@ -189,15 +191,17 @@ postgresVersion: 14
 #   # endpoint specifies the S3 endpoint to use.
 #   endpoint: ""
 #   # region specifies the S3 region to use. If your S3 storage system does not
-#   # use "region", fill this in with a random vaule.
+#   # use "region", fill this in with a random value.
 #   region: ""
 #   # key is the S3 key. This is stored in a Secret.
 #   key: ""
-#   # keySecret is the S3 key secret. This is tored in a Secret.
+#   # keySecret is the S3 key secret. This is stored in a Secret.
 #   keySecret: ""
+#   # keyType can be configured to enable IAM integration via AssumeRole
+#   keyType: ""
 #   # encryptionPassphrase is an optional parameter to enable encrypted backups
 #   # with pgBackRest. This is encrypted by pgBackRest and does not use S3's
-#   # built-in encrpytion system.
+#   # built-in encryption system.
 #   encryptionPassphrase: ""
 
 # gcs allows for Google Cloud Storage (GCS) to be used for backups. This allows
@@ -217,7 +221,7 @@ postgresVersion: 14
 # azure:
 #   # account is the name of the Azure account to be used.
 #   account: ""
-#   # key is the Secret key used associated with the Azure acount.
+#   # key is the Secret key used associated with the Azure account.
 #   key: ""
 #   # container is the Azure container that the backups will be stored in.
 #   container: ""
@@ -230,8 +234,8 @@ postgresVersion: 14
 # You can't set "multiBackupRepos" and any of the individual quickstarts at the
 # same time. "multiBackupRepos" will take precedence.
 #
-# Below is an example that enables one of each backup type. Note all of the
-# available quickstart options are presented below; please see the backup types
+# Below is an example that enables one of each backup type.
+# All available quickstart options are presented below; please see the backup types
 # if you want to see how each option works.
 # multiBackupRepos:
 # - volume:
@@ -242,6 +246,7 @@ postgresVersion: 14
 #     region: ""
 #     key: ""
 #     keySecret: ""
+#     keyType: ""
 # - gcs:
 #     bucket: ""
 #     key: |
@@ -259,15 +264,15 @@ postgresVersion: 14
 # Pooling / pgBouncer Settings #
 ################################
 
-# pgBouncerConfig sets all of the pgBouncer portion of the spec except for
+# pgBouncerConfig sets all of the pgBouncer portions of the spec except for
 # image. To set image, you need to set the "pgBouncer" setting.
 # pgBouncerConfig: {}
 
 #######################
 # Monitoring Settings #
 #######################
 
-# monitoringConfig sets all of the monitoring portion of the spec except for the
+# monitoringConfig sets all of the monitoring portions of the spec except for the
 # image. To set the image, which also enables monitoring, you need to set the
 # "monitoring" setting.
 # monitoringConfig: {}
@@ -278,7 +283,7 @@ postgresVersion: 14
 
 # metadata contains any metadata that should be applied to all PGO managed
 # objects in this Postgres cluster. This includes "annotations" and "labels" as
-# subkeys.
+# sub-keys.
 # metadata: {}
 
 # service customizes the Service that exposes the Postgres primary.
@@ -294,7 +299,7 @@ postgresVersion: 14
 # imagePullSecrets: []
 
 # supplementalGroups sets any group IDs that should be assigned to
-# Pods, particularly around file system contraints within a system
+# Pods, particularly around file system constraints within a system
 # supplementalGroups: []
 
 # disableDefaultPodScheduling if set to true, will disable any of the default
@@ -303,8 +308,8 @@ postgresVersion: 14
 # be used in addition to any customizations that are added in.
 # disableDefaultPodScheduling: false
 
-# openshift can set explicitly if this is an OpenShift cluster, or a cluster
+# openshift can be set explicitly if this is an OpenShift cluster or a cluster
 # that uses a SecurityContextConstraint. This usually does not need to be set,
-# but you may want to explicitly set it to "false" when using a SCC like
+# but you may want to explicitly set it to "false" when using an SCC like
 # "anyuid"
 # openshift: false

kustomize/azure/postgres.yaml

@@ -3,8 +3,8 @@ kind: PostgresCluster
 metadata:
   name: hippo-azure
 spec:
-  image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-14.6-2
-  postgresVersion: 14
+  image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-15.2-0
+  postgresVersion: 15
   instances:
     - dataVolumeClaimSpec:
         accessModes:
@@ -14,7 +14,7 @@ spec:
             storage: 1Gi
   backups:
     pgbackrest:
-      image: registry.developers.crunchydata.com/crunchydata/crunchy-pgbackrest:ubi8-2.41-2
+      image: registry.developers.crunchydata.com/crunchydata/crunchy-pgbackrest:ubi8-2.41-4
       configuration:
       - secret:
           name: pgo-azure-creds

kustomize/certmanager/README.md

@@ -11,7 +11,7 @@ This example shows how to use custom self-signed certificates generated by Cert-
 The first step is to deploy Cert-Manager to the Kubernetes cluster.  To do this, follow the instructions on the Cert-Manager website (https://cert-manager.io/docs/installation/).
 
 ## Setup Certificate Issuer
-After Cert-Manager has been deployed, the next step used in this example is to setup a Certificate Issuer.  The Certificate Issuer can be configured to be local to a namespace or cluster wide.  In the examples provided here, a cluster wide issuer is created.
+After Cert-Manager has been deployed, the next step used in this example is to set up a Certificate Issuer.  The Certificate Issuer can be configured to be local to a namespace or cluster wide.  In the examples provided here, a cluster wide issuer is created.
 
 ### Configure Issuer
 
@@ -25,7 +25,7 @@ This Kustomize deployment performs the following actions:
 * Generates a common CA certificate.
 * Creates a cluster wide (ClusterIssuer) CA certificate issuer using the generated CA certificate.
 
-By default the issues are created in the cert-manager namespace which is the default namespace for Cert-Manager.
+By default, the issues are created in the cert-manager namespace which is the default namespace for Cert-Manager.
 
 The CA certificate issuer is important as the Postgres components require that the ca.crt be the same for the certificates generated to support Postgres.