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

This commit is contained in:
Story Crater Bot
2026-08-22 23:40:13 -07:00
parent 600e148557
commit 23033bd7ef
+5 -12
View File
@@ -1,9 +1,6 @@
# Dedicated CNPG Postgres for Poimen Memory (GitOps, wave 2 — before poimen w3).
# Includes pgvector extension for semantic search (768-dim embeddings).
# Uses longhorn-imessage-local (WaitForFirstConsumer) to avoid volume binding
# 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).
# Dedicated CNPG Postgres for Poimen Memory (GitOps, wave 2).
# Uses default longhorn storage class (3 replicas, dataLocality disabled).
# CNPG generates secret `memory-db-app` + service `memory-db-rw` in ns poimen.
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
storageClass: longhorn-imessage-local
monitoring:
enablePodMonitor: true
size: 20Gi
storageClass: longhorn
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: