prole/supabase/helm/knoe-supabase/templates/kong
chrisfu 30df7d1c12 preserve: prole-specific OpenBao K8s-auth + Kong secret-bridge + phase2-3 canary runbook
Captured for the knoe-db convergence (Phase 2): configure_kubernetes_auth() (OpenBao
K8s auth → scoped knoe-jobs tokens vs root), the Kong knoe-secret route (secure-dropbox
bridge /secret/* → knoe-jobs:8081), and the prole.org canary-deploy runbook. None of
this is in canonical knoe-db — it is prole-staging-specific, not stale.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-21 14:42:27 -07:00
..
_helpers.tpl stabilize unattended GKE Supabase/CNPG deployment 2026-04-10 15:53:58 -07:00
backendconfig.yaml fix(net): GCE BackendConfig rejects type: TCP; switch to HTTP /healthz 2026-04-21 12:05:40 -07:00
config.yaml preserve: prole-specific OpenBao K8s-auth + Kong secret-bridge + phase2-3 canary runbook 2026-06-21 14:42:27 -07:00
deployment.yaml fix(cnpg,kong): wire cnpg-backup-sa, migrate PodMonitor, drop DASHBOARD consumer 2026-05-02 03:08:34 -07:00
ingress.yaml fix(net): BackendConfig healthchecks + externally-managed supabase-kong ingress 2026-04-21 10:31:06 -07:00
service.yaml fix(net): BackendConfig healthchecks + externally-managed supabase-kong ingress 2026-04-21 10:31:06 -07:00
serviceaccount.yaml stabilize unattended GKE Supabase/CNPG deployment 2026-04-10 15:53:58 -07:00