chrisfu 498a7f0412 Migrate Supabase to pi.prole.org, fix supabase_enabled override, monitoring PV vars ... Memory pressure on merlin (95% OOM with monitoring + CNPG replica + Supabase) resolved by moving Supabase workload to pi.prole.org which has headroom (49% memory, 2 pods). - conf/service/prole.cfg: set SUPABASE_PV_NODE, SUPABASE_PRIMARY_NODE=pi.prole.org, SUPABASE_STORAGE_CLASS=pi-local-iscsi, SUPABASE_PV_BASE_DIR for rancher local-path - supabase/helm/render_supabase.py: resolve SUPABASE_STORAGE_CLASS from env/cfg, apply pi-local-iscsi to storage/analytics PVCs, resolve DATABASE_NAMESPACE for correct db_host, DB_PASSWORD env override takes priority for live cluster password - supabase/deploy.sh: default SUPABASE_PV_NODE to pi.prole.org, default base dir to /var/lib/rancher/k3s/storage/supabase, add idempotent ALTER ROLE password sync, live DB_PASSWORD resolution in helm_render_values from knoe-db-superuser secret - knoe/core/actions.py: stop overriding init_cluster.supabase_enabled to False in silent mode so prole.cfg value is honored end-to-end - etc/init_monitoring.sh: derive pv_prom/pv_am/pv_graf inline before Released-PV loop to fix unbound variable error on idempotent monitoring installs Co-authored-by: Junie <junie@jetbrains.com>		2026-03-24 12:01:02 -07:00
..
prole.cfg	Migrate Supabase to pi.prole.org, fix supabase_enabled override, monitoring PV vars	2026-03-24 12:01:02 -07:00