Merge pull request #130 from cybertec-postgresql/rc-0.9.1

Rc 0.9.1

Author: Schmaetz

.github/ISSUE_TEMPLATE/postgres-operator-issue-template.md

@@ -1,19 +1,70 @@
 ---
-name: Postgres Operator issue template
+name: CYBERTEC-PG-Operator issue template
 about: How are you using the operator?
-title: ''
+title: '[BUG] Brief description of the problem'
 labels: ''
 assignees: ''
 
 ---
 
-Please, answer some short questions which should help us to understand your problem / question better?
+To quickly narrow down the problem, we need details about your infrastructure.
 
-- **Which image of the operator are you using?** e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.10.1
-- **Where do you run it - cloud or metal? Kubernetes or OpenShift?** [AWS K8s | GCP ... | Bare Metal K8s]
-- **Are you running Postgres Operator in production?** [yes | no]
-- **Type of issue?** [Bug report, question, feature request, etc.]
+- **Operator version / image:** [e.g. docker.io/cybertecpostgresql/cybertec-pg-operator:v0.9.0-1]
+- **Postgres Docker Image:** [e.g., containers.cybertec.at/cybertec-pg-container/postgres:rocky9-18.1-1]
+- **Kubernetes Platform:** [Please check or add]
+    - [ ] Vanilla Kubernetes (Bare Metal / VM)
+    - [ ] OpenShift
+    - [ ] Rancher / RKE / RKE2
+    - [ ] AWS EKS
+    - [ ] Google GKE
+    - [ ] Azure AKS
+    - [ ] Minikube / Kind / K3s
+    - [ ] Other: ________
+- **Kubernetes version:** [Output of `kubectl version`, e.g. v1.28.3]
+- **Storage Class:** [e.g., standard, gp2, longhorn, ceph-rbd]
+- **Is the operator running in production?** [Yes / No]
 
-Some general remarks when posting a bug report:
-- Please, check the operator, pod (Patroni) and postgresql logs first. When copy-pasting many log lines please do it in a separate GitHub gist together with your Postgres CRD and configuration manifest.
-- If you feel this issue might be more related to the [Spilo](https://github.com/zalando/spilo/issues) docker image or [Patroni](https://github.com/zalando/patroni/issues), consider opening issues in the respective repos.
+---
+
+### Problem Description
+
+**What happened?**
+Describe the unexpected behavior.
+
+**What did you expect?**
+Describe what should have happened.
+
+---
+
+### Steps to reproduce
+
+How can we reproduce the problem?
+1. Applied Postgres cluster manifest (see below)
+2. Executed command: `...`
+3. Error occurs when ...
+
+---
+
+### Relevant logs and manifests
+
+**IMPORTANT:** Please use code blocks (```) to format logs and YAML files in a readable way.
+
+**1. Operator logs:**
+(Please check the logs of the operator pod for errors)
+```text
+Insert logs here...
+```
+
+**2. Postgres / Patroni /pgBackRest logs: (If the pod starts but the DB is not running):**
+(Please check the logs of the postgres or pgbackrest pod for errors)
+```text
+Insert logs here...
+```
+
+**3. Postgres Cluster Manifest (YAML): (Please remove passwords or sensitive data!)**
+```yaml
+Insert Manifest here...
+```
+
+**Additional information**
+Are there any special circumstances in your setup? (e.g., service mesh such as Istio/Linkerd, special network policies, air-gapped environment?)

.github/PULL_REQUEST_TEMPLATE/postgres-operator-pull-request-template.md

@@ -1,18 +1,27 @@
-## Problem description
-
-
-
-## Linked issues
+## Description
+## Type of Change
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Documentation update
 
 
+## Linked Issues
+---
 
 ## Checklist
 
-Thanks for submitting a pull request to the Postgres Operator project.
-Please, ensure your contribution matches the following items:
+Thanks for submitting a pull request to the CYBERTEC-pg-operator project!
+Please ensure your contribution matches the following items:
+
+- [ ] **Code Formatting:** My code follows the Go formatting standards. (Your IDE should do this automatically, or run `go fmt`).
+- [ ] **Generated Code:** I have updated [generated code](https://cybertec-postgresql.github.io/CYBERTEC-pg-operator/contribution#code-generation) (clientset, deepcopy) when introducing new fields to the `cpo.opensource.cybertec.at` API package.
+- [ ] **Configuration & CRDs:** New [configuration options](https://cybertec-postgresql.github.io/CYBERTEC-pg-operator/contribution#introduce-additional-configuration-parameters) are reflected in:
+    - [ ] The Go struct definitions
+    - [ ] The CRD validation manifests (YAML)
+    - [ ] The Helm Charts
+    - [ ] The sample manifests
+- [ ] **Tests:** New functionality is covered by [unit tests](https://cybertec-postgresql.github.io/CYBERTEC-pg-operator/contribution#unit-tests) and/or [e2e tests](https://cybertec-postgresql.github.io/CYBERTEC-pg-operator/contribution#end-to-end-tests).
+- [ ] **Existing PRs:** I have checked existing open PRs to ensure there are no duplicates or conflicts.
 
-- [ ] Your go code is [formatted](https://blog.golang.org/gofmt). Your IDE should do it automatically for you.
-- [ ] You have updated [generated code](https://github.com/zalando/postgres-operator/blob/master/docs/developer.md#code-generation) when introducing new fields to the `acid.zalan.do` api package.
-- [ ] New [configuration options](https://github.com/zalando/postgres-operator/blob/master/docs/developer.md#introduce-additional-configuration-parameters) are reflected in CRD validation, helm charts and sample manifests.
-- [ ] New functionality is covered by [unit](https://github.com/zalando/postgres-operator/blob/master/docs/developer.md#unit-tests) and/or [e2e](https://github.com/zalando/postgres-operator/blob/master/docs/developer.md#end-to-end-tests) tests.
-- [ ] You have checked existing open PRs for possible overlay and referenced them.
+## How has this been tested?

README.md

@@ -75,6 +75,7 @@ This architecture forms the basis for a modern, highly available and scalable Po
 | 0.8.0   | 13 - 17    | 2.53       | 4.0.2   | 1.21+      | 1.21.7  |
 | 0.8.3   | 13 - 17    | 2.54+      | 4.0.5   | 1.21+      | 1.22.12 |
 | 0.9.0   | 13 - 18    | 2.56+      | 4.1.0   | 1.21+      | 1.25.2  |
+| 0.9.1   | 13 - 18    | 2.56+      | 4.1.0   | 1.21+      | 1.25.6  |
 
 --- 
 

charts/postgres-cluster/Chart.yaml

@@ -3,9 +3,9 @@ name: postgres-cluster
 description: Deploys a PostgreSQL cluster using the PostgreSQL operator
 
 type: application
-version: 0.8.0
+version: 0.9.1
 
-appVersion: "0.8.0-1"
+appVersion: "0.9.1-1"
 
 maintainers:
   - name: CYBERTEC PostgreSQL International GmbH

charts/postgres-cluster/index.yaml

@@ -12,11 +12,11 @@
 #  my-annotation: value
 
 cluster:
-  dockerImage: docker.io/cybertecpostgresql/cybertec-pg-container:postgres-18.0-1
+  dockerImage: containers.cybertec.at/cybertec-pg-container/postgres:rocky9-18.1-1
   numberOfInstances: 2
 
   postgresql:
-    version: "17"
+    version: "18"
     #parameters:
     #  work_mem: "40MB"
 
@@ -25,7 +25,7 @@ cluster:
   #  value: custom
 
   volume:
-    size: 1Gi
+    size: 5Gi
     #storageClass: my-storage
     #selector:
     #  matchExpressions:
@@ -45,7 +45,7 @@ cluster:
 
   resources:
     requests:
-      cpu: 10m
+      cpu: 100m
       memory: 100Mi
     limits:
       cpu: 500m
@@ -63,13 +63,19 @@ cluster:
     failsafe_mode: false
     initdb:
       encoding: "UTF8"
-      locale: "C.UTF-8"
-      data-checksums: "true"
+      locale: "en_US.UTF-8"
+      locale-provider: "icu"
+      icu-locale: "en_US"
     pg_hba:
-    - local   all         all               trust
-    - local   replication standby           trust
-    - host    replication standby all       scram-sha-256
-    - host    all         all     all       scram-sha-256
+      - local     all             all                                 trust
+      - hostssl   all             +cpo_pam            127.0.0.1/32    pam
+      - host      all             all                 127.0.0.1/32    scram-sha-256
+      - hostssl   all             +cpo_pam            ::1/128         pam
+      - host      all             all                 ::1/128         scram-sha-256
+      - local     replication     cpo_replication                     trust
+      - hostssl   replication     cpo_replication     all             scram-sha-256
+      - hostnossl all             all                 all             reject
+      - hostssl   all             all                 all             scram-sha-256
     #slots:
     #  permanent_physical_1:
     #    type: physical
@@ -95,9 +101,13 @@ cluster:
     synchronous_node_count: 1
     maximum_lag_on_failover: 33554432
 
+  #monitor:
+  #  image: "containers.cybertec.at/cybertec-pg-container/exporter:rocky9-18.1-2"
+
+
   #backup:
   #  pgbackrest:
-  #    image: "docker.io/cybertecpostgresql/cybertec-pg-container:pgbackrest-17.0-1"
+  #    image: "containers.cybertec.at/cybertec-pg-container/pgbackrest:rocky9-18.1-1"
   #    configuration:
   #      secret: "xyz"
   #      protection:
@@ -123,7 +133,11 @@ cluster:
   #      id: "unique restore identifier"
   #      repo: repo1
   #      options:
-  #        target-time: "2023-01-02 03:04:05+06"
+  #        target-time: "2026-01-02 03:04:05+01"
+
+  #tde: # Only usable if you have an active PGEE subscription and access to the PGEE images, which must be entered under cluster.dockerImage.
+  #  enable: true
+  #  keybits: 256
 
   #users:  # Application/Robot users
   #  appadmin:
@@ -179,7 +193,7 @@ cluster:
   #  cluster: name-of-cluster-to-clone
 
   #connectionPooler:
-  #  dockerImage: docker.io/cybertecpostgresql/cybertec-pg-container:pgbouncer-1.23-2
+  #  dockerImage: containers-cybertec.at/cybertec-pg-container/pgbouncer:rocky9-1.25-1
   #  numberOfInstances: 2
   #  mode: transaction # session/transaction mode pooling
   #  schema: "pooler"

charts/postgres-cluster/postgres-cluster-0.8.0.tgz

@@ -1,7 +1,7 @@
 apiVersion: v2
 name: postgres-operator
-version: 0.8.0
-appVersion: 0.8.0
+version: 0.9.1
+appVersion: 0.9.0-1
 home: https://github.com/cybertec-postgresql/cybertec-pg-operator
 description: Postgres Operator creates and manages PostgreSQL clusters running in Kubernetes
 keywords:

charts/postgres-cluster/values.yaml

@@ -3,8 +3,11 @@ kind: CustomResourceDefinition
 metadata:
   name: operatorconfigurations.cpo.opensource.cybertec.at
   labels:
-    app.kubernetes.io/name: postgres-operator
+    app.kubernetes.io/name: cpo
+    app.kubernetes.io/version: {{ .Chart.Version }}
 spec:
+  conversion:
+    strategy: None
   group: cpo.opensource.cybertec.at
   names:
     kind: OperatorConfiguration
@@ -336,6 +339,9 @@ spec:
                   spilo_allow_privilege_escalation:
                     type: boolean
                     default: true
+                  container_readonly_root_filesystem:
+                    type: boolean
+                    default: false
                   spilo_runasuser:
                     type: integer
                   spilo_runasgroup:
@@ -653,7 +659,7 @@ spec:
                     default: "pooler"
                   connection_pooler_image:
                     type: string
-                    default: "registry.opensource.zalan.do/acid/pgbouncer:master-27"
+                    default: "containers.cybertec.at/cybertec-pg-container/pgbouncer:rocky9-1.25-2"
                   connection_pooler_max_db_connections:
                     type: integer
                     default: 60

charts/postgres-operator/Chart.yaml

@@ -694,6 +694,19 @@ spec:
                             type: string
                           recoveryEventType:
                             type: string
+              tde:
+                nullable: true
+                properties:
+                  enable:
+                    type: boolean
+                  keybits: 
+                    type: integer
+                    format: int32
+                    default: 128
+                    enum:
+                      - 128
+                      - 192
+                      - 256
               teamId:
                 type: string
               tls: