chore: remove images entirely from charts

bcgov · Jan 9, 2025 · b90e611 · b90e611
1 parent 4d8ecdd
commit b90e611
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 10 deletions.
diff --git a/charts/crunchy/templates/PostgresCluster.yaml b/charts/crunchy/templates/PostgresCluster.yaml
@@ -7,9 +7,6 @@ metadata:
 spec:
   metadata:
     labels: {{ include "crunchy-postgres.labels" . | nindent 6 }}
-  {{ if .Values.crunchy.crunchyImage }}
-  image: {{ .Values.crunchy.crunchyImage }}
-  {{ end }}
   imagePullPolicy: {{.Values.crunchy.imagePullPolicy}}
   postgresVersion: {{ .Values.crunchy.postgresVersion }}
   {{ if .Values.crunchy.postGISVersion }}
@@ -115,9 +112,6 @@ spec:
     {{- if .Values.crunchy.pgBackRest.enabled }}
   backups:
     pgbackrest:
-      {{ if .Values.crunchy.pgBackRest.image }}
-      image: {{ .Values.crunchy.pgBackRest.image }}
-      {{ end }}
       {{- if .Values.crunchy.pgBackRest.s3.enabled}}
       configuration:
         - secret:

diff --git a/charts/crunchy/values.yaml b/charts/crunchy/values.yaml
@@ -3,8 +3,6 @@ global:
     dbName: app #test
 crunchy: # enable it for TEST and PROD, for PR based pipelines simply use single postgres
   enabled: true
-  # it is recommended by platform team , not to use explicit images
-  #crunchyImage: artifacts.developer.gov.bc.ca/bcgov-docker-local/crunchy-postgres-gis:ubi8-16.2-3.4-0
   postgresVersion: 16
   postGISVersion: '3.4'
   imagePullPolicy: IfNotPresent
@@ -49,8 +47,6 @@ crunchy: # enable it for TEST and PROD, for PR based pipelines simply use single
     enabled: true
     backupPath: /backups/test/cluster/version # change it for PROD, create values-prod.yaml
     clusterCounter: 1 # this is the number to identify what is the current counter for the cluster, each time it is cloned it should be incremented.
-    # it is recommended by platform team , not to use explicit images
-    # image: artifacts.developer.gov.bc.ca/bcgov-docker-local/crunchy-pgbackrest:ubi8-2.49-0
     # If retention-full-type set to 'count' then the oldest backups will expire when the number of backups reach the number defined in retention
     # If retention-full-type set to 'time' then the number defined in retention will take that many days worth of full backups before expiration
     retentionFullType: count