Fix: memory-db use default longhorn (3 replicas), 20Gi

k8s/infra/databases/memory-db.yaml

@@ -1,9 +1,6 @@
-# Dedicated CNPG Postgres for Poimen Memory (GitOps, wave 2 — before poimen w3).
+# Dedicated CNPG Postgres for Poimen Memory (GitOps, wave 2).
-# Includes pgvector extension for semantic search (768-dim embeddings).
+# Uses default longhorn storage class (3 replicas, dataLocality disabled).
-# Uses longhorn-imessage-local (WaitForFirstConsumer) to avoid volume binding
+# CNPG generates secret `memory-db-app` + service `memory-db-rw` in ns poimen.
-# issues when pod gets scheduled to nodes with unhealthy Longhorn replicas.
-# CNPG generates secret `memory-db-app` + service `memory-db-rw` in ns poimen;
-# poimen reads them locally (no cross-ns secret copy).
 apiVersion: postgresql.cnpg.io/v1
 kind: Cluster
 metadata:
@@ -28,13 +25,9 @@ spec:
     requests: { memory: "512Mi", cpu: "250m" }
     limits: { memory: "2Gi", cpu: "1" }
   storage:
-    size: 10Gi
+    size: 20Gi
-    storageClass: longhorn-imessage-local
+    storageClass: longhorn
-  monitoring:
-    enablePodMonitor: true
   affinity:
-    # preferred + tolerations: HA across nodes without deadlocking a partly-
-    # schedulable 3-CP (same as temporal/authentik-db).
     podAntiAffinityType: preferred
     topologyKey: kubernetes.io/hostname
     tolerations: