docs(lockdown): durable pg-proxy role-gate DONE — shipped, deployed, verified#64
Merged
Merged
Conversation
…d+verified) The churn-proof PG_PROXY_DENIED_ROLES role-gate is now live in prod (InstaNode-dev/instant-pg-proxy PR #1, image v0.2.0, deployed with PG_PROXY_DENIED_ROLES=instanode_admin,instant_cust,postgres,doadmin). Live-verified pod-IP-independent: external admin rejected at the PROXY layer (28000) even though the proxy now runs on new IPs the pg_hba reject lines don't name; customer usr_* still forwarded; in-cluster provisioning via ClusterIP svc unaffected. The pg_hba proxy-IP reject lines are now redundant belt-and-suspenders. Updates §3a (churn warning → mitigated), §7 (scope), §9 Drill Log (new row + follow-up closed). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Marks the durable, churn-proof closer for the truehomie public-admin vector as DONE in
POSTGRES-CUSTOMERS-LOCKDOWN-RUNBOOK.md.The
PG_PROXY_DENIED_ROLESrole-gate is now live in prod:InstaNode-dev/instant-pg-proxy(created — did not exist before), PR feat(k8s): add image-puller DaemonSet to pre-warm node image caches #1 (merge5a86c93)ghcr.io/mastermanas805/instant-pg-proxy:v0.2.0, deployed withPG_PROXY_DENIED_ROLES=instanode_admin,instant_cust,postgres,doadminLive-verified pod-IP-independent: after rollout the proxy runs on NEW IPs (
10.109.6.132/10.109.4.98) that the pg_hba reject lines do NOT name, yet external admin (instanode_admin/instant_cust/postgres) overpg.instanode.devis rejected at the proxy layer (FATAL 28000 "role is not permitted over the public endpoint"), not pg_hba. Customerusr_*still forwarded; in-cluster provisioning via the ClusterIP svc unaffected (instant_custCREATE/DROP OK;pg_database_sizeread OK).The pg_hba proxy-IP reject lines are now redundant belt-and-suspenders (left in place, harmless). Updates §3a, §7, §9.
🤖 Generated with Claude Code