feat(functions): route edge functions through PgBouncer poolers

[h0lybyte]

Summary

• Switches Edge Functions SUPABASE_DB_URL from direct supabase-cluster-rw to supabase-cluster-pooler-rw (PgBouncer transaction mode, 3 instances)
• Adds SUPABASE_DB_URL_RO pointing to supabase-cluster-pooler-ro (PgBouncer session mode, 2 instances) for read-only queries
• First service migrated under [PG] Deploy CNPG Pooler (PgBouncer) and migrate services from direct -rw connections #7593 Phase 2

Details

Edge Functions primarily use the Supabase SDK via Kong/PostgREST (RPC calls), but the SUPABASE_DB_URL env var is available for direct DB access by the edge runtime. Routing through the pooler:

• Reduces direct connections to PostgreSQL
• Enables connection multiplexing for short-lived function invocations
• The RO URL allows read-heavy routes (feeds, lookups) to use replica poolers

Test plan

• Verify supabase-shared secret is refreshed with new db-url and db-url-ro keys
• Confirm Edge Functions pod restarts with the new env vars
• Test edge function endpoints (meme feed, MC player, health check)
• Verify no errors in edge function logs related to DB connectivity
• Check PgBouncer stats: kubectl exec <pooler-pod> -n kilobase -- pgbouncer -d /tmp/pgbouncer.ini -R

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None