From 0ad5dbe7411bc0b34efe3211d689e5239fc7cbd4 Mon Sep 17 00:00:00 2001
From: Hermes Agent service account
 <hermes@carousel-of-progress.local.mk-labs.cloud>
Date: Thu, 4 Jun 2026 20:34:25 -0500
Subject: [PATCH] fix(harbor): remove invalid secretName parameter from core
 config

The secretName parameter was being used as a literal secret name
'CORE_SECRET' which doesn't exist. This caused harbor-core pods to
fail mounting volumes.

The correct approach is to use existingSecret for credential keys,
and let Harbor manage its own internal secrets.
---
 cluster/platform/harbor/values.yaml | 1 -
 1 file changed, 1 deletion(-)

diff --git a/cluster/platform/harbor/values.yaml b/cluster/platform/harbor/values.yaml
index 8534760..5b5f258 100644
--- a/cluster/platform/harbor/values.yaml
+++ b/cluster/platform/harbor/values.yaml
@@ -131,7 +131,6 @@ core:
   # Core secret from ExternalSecret
   secret: ""
   existingSecret: "harbor-credentials"
-  secretName: "CORE_SECRET"
   # Enable HTTP/2 for better performance
   configureUserSettings: |-
     http2_push_preload on;