add all needed configs for pg18 support

Author: Schmaetz

charts/postgres-cluster/values.yaml

@@ -12,7 +12,7 @@
 #  my-annotation: value
 
 cluster:
-  dockerImage: docker.io/cybertecpostgresql/cybertec-pg-container:postgres-17.0-2
+  dockerImage: docker.io/cybertecpostgresql/cybertec-pg-container:postgres-17.6-1
   numberOfInstances: 2
 
   postgresql:

charts/postgres-operator-ui/templates/deployment.yaml

@@ -84,6 +84,7 @@ spec:
                   "limit_iops": 16000,
                   "limit_throughput": 1000,
                   "postgresql_versions": [
+                    "18",
                     "17",
                     "16",
                     "15",

charts/postgres-operator/crds/postgresqls.yaml

@@ -546,6 +546,7 @@ spec:
                       - "15"
                       - "16"
                       - "17"
+                      - "18"
                   parameters:
                     type: object
                     additionalProperties:

docs/hugo/content/en/first_cluster/_index.md

@@ -16,7 +16,7 @@ kind: postgresql
 metadata:
   name: cluster-1
 spec:
-  dockerImage: "docker.io/cybertecpostgresql/cybertec-pg-container:postgres-17.4-1"
+  dockerImage: "docker.io/cybertecpostgresql/cybertec-pg-container:postgres-17.6-1"
   numberOfInstances: 1
   postgresql:
     version: "17"

docs/hugo/content/en/ha_cluster/_index.md

@@ -30,7 +30,7 @@ kind: postgresql
 metadata:
   name: cluster-1
 spec:
-  dockerImage: "docker.io/cybertecpostgresql/cybertec-pg-container:postgres-17.4-1"
+  dockerImage: "docker.io/cybertecpostgresql/cybertec-pg-container:postgres-17.6-1"
   numberOfInstances: 2
   postgresql:
     version: "17"

docs/hugo/content/en/pg_versioning/major_upgrades.md

@@ -61,13 +61,13 @@ CPO enables the use of the in-place upgrade, which makes it possible to upgrade
 ```
 spec:
   postgresql:
-    version: "17"
+    version: "18"
 ```
 To trigger an In-Place-Upgrade you have just to increase the parameter `spec.postgresql.version`. If you choose a valid number the Operator will start with the prozedure, described above. 
 
 ```sh
 kubectl patch postgresqls.cpo.opensource.cybertec.at cluster-1 --type='merge' -p \
-'{"spec":{"postgresql":{"version":"17"}}}'
+'{"spec":{"postgresql":{"version":"18"}}}'
 ```
 
 ## Upgrade on cloning

manifests/postgresql.crd.yaml

@@ -544,6 +544,7 @@ spec:
                       - "15"
                       - "16"
                       - "17"
+                      - "18"
                   parameters:
                     type: object
                     additionalProperties:

pkg/apis/cpo.opensource.cybertec.at/v1/crds.go

@@ -728,9 +728,6 @@ var PostgresCRDResourceValidation = apiextv1.CustomResourceValidation{
 							"version": {
 								Type: "string",
 								Enum: []apiextv1.JSON{
-									{
-										Raw: []byte(`"12"`),
-									},
 									{
 										Raw: []byte(`"13"`),
 									},
@@ -746,6 +743,9 @@ var PostgresCRDResourceValidation = apiextv1.CustomResourceValidation{
 									{
 										Raw: []byte(`"17"`),
 									},
+									{
+										Raw: []byte(`"18"`),
+									},
 								},
 							},
 							"parameters": {

pkg/cluster/majorversionupgrade.go

@@ -11,14 +11,12 @@ import (
 
 // VersionMap Map of version numbers
 var VersionMap = map[string]int{
-	"10": 100000,
-	"11": 110000,
-	"12": 120000,
 	"13": 130000,
 	"14": 140000,
 	"15": 150000,
 	"16": 160000,
 	"17": 170000,
+	"18": 180000,
 }
 
 // IsBiggerPostgresVersion Compare two Postgres version numbers

ui/manifests/deployment.yaml

@@ -72,6 +72,7 @@ spec:
                   "limit_iops": 16000,
                   "limit_throughput": 1000,
                   "postgresql_versions": [
+                    "18",
                     "17",
                     "16",
                     "15",