diff --git a/quickstart-postgresql/templates/cluster.yaml b/quickstart-postgresql/templates/cluster.yaml
index f3cdbca..8098799 100644
--- a/quickstart-postgresql/templates/cluster.yaml
+++ b/quickstart-postgresql/templates/cluster.yaml
@@ -22,7 +22,11 @@ spec:
       database: {{ include "postgresql.fullname" . }}
       dataChecksums: {{ .Values.bootstrap.initdb.dataChecksums }}
   primaryUpdateStrategy: {{ .Values.primaryUpdateStrategy }}
-  imageName: ghcr.io/cloudnative-pg/postgresql:15.3
+  {{- with .Values.imageName }}
+  imageName: {{ . }}
+  {{- else }}
+  imageCatalogRef: {{ .Values.imageCatalogRef | toYaml | nindent 4 }}
+  {{- end }}
   storage:
     {{- with .Values.storage.storageClass }}
     storageClass: {{ . }}
diff --git a/quickstart-postgresql/values.yaml b/quickstart-postgresql/values.yaml
index 65c1353..e8c6681 100644
--- a/quickstart-postgresql/values.yaml
+++ b/quickstart-postgresql/values.yaml
@@ -7,6 +7,28 @@ fullnameOverride: ''
 ## default set to 2 for smooth migration between nodes
 instances: 2
 
+## @param postgresMajor Major version of PostgreSQL to be used
+## This specifies the major version of PostgreSQL to deploy. 
+## Ensure compatibility with any extensions or configuration settings.
+## Allowed values are 15 and 17.
+
+
+## @param imageName Fully qualified image name for the PostgreSQL container
+## When set, this takes precedence over the `imageCatalogRef` parameter.
+## Use this to specify an exact container image for deployment.
+## Set to `null` if `imageCatalogRef` should be used instead.
+imageName: null
+
+## @param imageCatalogRef Reference to a ClusterImageCatalog resource for PostgreSQL
+## Specifies the catalog reference for resolving the PostgreSQL container image.
+## Ignored if `imageName` is set.
+## Use this to dynamically resolve the image based on the catalog. More info: https://cloudnative-pg.io/documentation/1.24/image_catalog/
+imageCatalogRef:
+  apiGroup: postgresql.cnpg.io
+  kind: ClusterImageCatalog
+  name: platform
+  major: 17
+
 # @param primaryUpdateStrategy Rolling update strategy
 # Select between unsupervised (automated update of the primary once all
 # replicas have been upgraded) or supervised (requires manual supervision to perform