fix(platform): inject ELASTIC_PASSWORD from platform secrets in production

Backend validate-production-config requires a non-default ELASTIC_PASSWORD; read it from abrban-platform-secrets.elastic-password like other credentials. Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-03 19:24:34 +03:30
parent d3bbc0c0a0
commit a2fe61b1f6
3 changed files with 9 additions and 2 deletions
@@ -3,7 +3,8 @@
 # Real SealedSecret lives in cloud-host-gitops/sealed-secrets/ — never commit plaintext passwords.
 #
 # Required keys (must match backend Deployment + validate-production-config):
-#   postgres-password, jwt-secret, jwt-refresh-secret, cluster-kubeconfig-key, redis-password
+#   postgres-password, jwt-secret, jwt-refresh-secret, cluster-kubeconfig-key,
+#   redis-password, elastic-password (must match elasticsearch-credentials in logging)
 #
 # Generate (replace CHANGE_ME_* with strong random values):
 #
@@ -13,6 +14,7 @@
 #     --from-literal=jwt-refresh-secret='CHANGE_ME_REFRESH_32CHARS_MIN' \
 #     --from-literal=cluster-kubeconfig-key='0123456789abcdef0123456789abcdef' \
 #     --from-literal=redis-password='CHANGE_ME_REDIS' \
+#     --from-literal=elastic-password='CHANGE_ME_ELASTIC' \
 #     --dry-run=client -o json \
 #   | kubeseal \
 #       --controller-name=sealed-secrets-controller \