FIX(app): add postgresql ExternalSecret

- postgresql 네임스페이스의 secret을 mas 네임스페이스에서 참조할 수 없는 문제 해결
- ExternalSecret을 통해 mas 네임스페이스에도 동일한 secret 생성

deploy/k8s/base/kustomization.yaml

@@ -4,6 +4,7 @@ kind: Kustomization
 resources:
   - deployment.yaml
   - service.yaml
+  - ../../vault/mas-postgres.yaml
 
 commonLabels:
   app.kubernetes.io/name: mas

deploy/k8s/overlays/prod/kustomization.yaml

@@ -16,5 +16,5 @@ commonLabels:
 # 이미지 태그 설정 (ArgoCD Image Updater가 자동으로 업데이트)
 images:
   - name: gitea0213.kro.kr/bluemayne/mas
-    newTag: main-sha-e5ac54f869099f9e8b27618760c411a30e4372b7
+    newTag: main-sha-476581d4ff9af3aa80218edc7af6ffb51b39c099
 

deploy/vault/mas-postgres.yaml

@@ -1,7 +1,7 @@
 apiVersion: external-secrets.io/v1beta1
 kind: ExternalSecret
 metadata:
-  name: mas-postgres
+  name: postgresql-password
   namespace: mas
 spec:
   refreshInterval: 1h
@@ -9,11 +9,15 @@ spec:
     kind: ClusterSecretStore
     name: vault-backend
   target:
-    name: mas-postgres
+    name: postgresql-password
     creationPolicy: Owner
   data:
     - secretKey: password
       remoteRef:
-        key: mas/postgres
+        key: databases/postgresql
         property: PASSWORD
+    - secretKey: postgres-password
+      remoteRef:
+        key: databases/postgresql
+        property: POSTGRES_PASSWORD