feat(helm): allow using existing secret for S3

Author: plaffitt

helm/kube-image-keeper/templates/registry-deployment.yaml

@@ -59,15 +59,16 @@ spec:
               value: {{ $v | quote }}
             {{- end }}
             {{- end }}
+            {{ $s3KeysSecretName := .Values.registry.persistence.s3ExistingSecret | default (print (include "kube-image-keeper.fullname" . ) "-s3-registry-keys") }}
             - name: REGISTRY_STORAGE_S3_ACCESSKEY
               valueFrom:
                 secretKeyRef:
-                  name: {{ include "kube-image-keeper.fullname" . }}-s3-registry-keys
+                  name: {{ $s3KeysSecretName }}
                   key: accessKey
             - name: REGISTRY_STORAGE_S3_SECRETKEY
               valueFrom:
                 secretKeyRef:
-                  name: {{ include "kube-image-keeper.fullname" . }}-s3-registry-keys
+                  name: {{ $s3KeysSecretName }}
                   key: secretKey
             {{- range .Values.registry.env }}
             - name: {{ .name }}

helm/kube-image-keeper/values.yaml

@@ -144,6 +144,7 @@ registry:
     size: 20Gi
     # -- External S3 configuration (needed only if you don't enable minio) (see https://github.com/docker/docs/blob/main/registry/storage-drivers/s3.md)
     s3: {}
+    s3ExistingSecret: ""
   # -- Garbage collector cron schedule. Use standard crontab format.
   garbageCollectionSchedule: "0 0 * * 0"
   service: