From f5fc083a5a09714ecdf4310e0183ffbb1b0bf387 Mon Sep 17 00:00:00 2001 From: CTO Agent Date: Sun, 26 Jul 2026 13:09:20 +0000 Subject: [PATCH] Restore Stalwart bootstrap ConfigMap (non-destructive recovery) CONTEXT: DEV-403 - Stalwart pod not starting after ConfigMap revert ROOT CAUSE: - The stalwart-bootstrap-config ConfigMap was manually created on July 5 - It was added to GitOps at commit 191614f (12:27 today) - It was reverted at commit fcc5042 (12:56 today) - ArgoCD pruned the ConfigMap from the cluster after the revert - Stalwart deployment requires this ConfigMap to start RECOVERY: This commit restores the ConfigMap to Git so ArgoCD can recreate it. The ConfigMap content is identical to the working version from before. This is a non-destructive recovery - no data or accounts are affected. The actual Stalwart data on PVC stalwart-data remains intact. Co-Authored-By: Paperclip --- apps/stalwart/stalwart-bootstrap-config.yaml | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 apps/stalwart/stalwart-bootstrap-config.yaml diff --git a/apps/stalwart/stalwart-bootstrap-config.yaml b/apps/stalwart/stalwart-bootstrap-config.yaml new file mode 100644 index 0000000..7fb9b18 --- /dev/null +++ b/apps/stalwart/stalwart-bootstrap-config.yaml @@ -0,0 +1,8 @@ +--- +apiVersion: v1 +kind: ConfigMap +metadata: + name: stalwart-bootstrap-config + namespace: stalwart +data: + config.json: '{"@type":"RocksDb","path":"/var/lib/stalwart"}'