From 6fa51ad7ff2396d9829469150bd7958962144d25 Mon Sep 17 00:00:00 2001
From: pyratm <90207140+pyratm@users.noreply.github.com>
Date: Mon, 17 Jul 2023 19:57:24 +0100
Subject: [PATCH] Add registryctl env secretRef for S3 existingSecret

If s3.existingSecret has been set, ensure the there is an envFrom secretRef for the registryctl container

Signed-off-by: Ian <pyratm.21@gmail.com>
---
 templates/registry/registry-dpl.yaml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/templates/registry/registry-dpl.yaml b/templates/registry/registry-dpl.yaml
index adb5a73f5..fddba9fa8 100644
--- a/templates/registry/registry-dpl.yaml
+++ b/templates/registry/registry-dpl.yaml
@@ -188,6 +188,10 @@ spec:
             name: "{{ template "harbor.registry" . }}"
         - secretRef:
             name: "{{ template "harbor.registryCtl" . }}"
+        {{- if .Values.persistence.imageChartStorage.s3.existingSecret }}
+        - secretRef:
+            name: {{ .Values.persistence.imageChartStorage.s3.existingSecret }}
+        {{- end }}
         env:
         - name: CORE_SECRET
           valueFrom: