From 4feb6f7cc45404546359e732993a5b8c118e8649 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Florian=20M=C3=BCller?= <florian@tomueller.de>
Date: Thu, 4 Jun 2026 13:17:09 +0000
Subject: [PATCH] fix: Pin Superset SECRET_KEY in end-to-end-security stack

---
 stacks/end-to-end-security/superset.yaml | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/stacks/end-to-end-security/superset.yaml b/stacks/end-to-end-security/superset.yaml
index 376c52f3..a1c3d59c 100644
--- a/stacks/end-to-end-security/superset.yaml
+++ b/stacks/end-to-end-security/superset.yaml
@@ -1,4 +1,14 @@
 ---
+# The Superset metadata database is restored from postgres_superset_dump.sql (see
+# setup-postgresql.yaml), which contains rows (e.g. the Trino database connection
+# password) encrypted with the SECRET_KEY below.
+apiVersion: v1
+kind: Secret
+metadata:
+  name: superset-secret-key
+stringData:
+  SECRET_KEY: supersetSecretKey
+---
 apiVersion: superset.stackable.tech/v1alpha1
 kind: SupersetCluster
 metadata: