From 290c8b91f8cb2293676a766095eaefafd105ef25 Mon Sep 17 00:00:00 2001
From: Danijel Simeunovic <danijel.simeunovic@fortedigital.com>
Date: Mon, 27 Apr 2026 14:05:38 +0200
Subject: [PATCH] db pass

---
 infra/values/base/databunker-values.yaml | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/infra/values/base/databunker-values.yaml b/infra/values/base/databunker-values.yaml
index dbc1eaf..c79a2f7 100644
--- a/infra/values/base/databunker-values.yaml
+++ b/infra/values/base/databunker-values.yaml
@@ -24,6 +24,14 @@ ingress:
     enabled: true # Set to true to enable TLS
     secretName: "databunker-tls" # Name of the secret containing TLS certificate
 
+# Pin PostgreSQL password — chart uses randAlphaNum without lookup,
+# so each ArgoCD sync would regenerate the password while PVC keeps the old one.
+# Same issue as Backstage PostgreSQL (see MEMORY.md).
+internal:
+  postgresql:
+    auth:
+      password: "databunker-pg-pass-2026"
+
 resources:
   # Uncomment and adjust these values based on your requirements
   # requests: