feat(tb-dev): SecurityGroupPolicy assigning the Neon-client pod SG to keycloak#3
Merged
Merged
Conversation
… keycloak Assigns [EKS control-plane cluster SG, mzla-tb-dev-keycloak-customer-pod SG] to the keycloak-customer pods so they reach Neon over the stalwart-neondb-privatelink endpoint (its SG admits only allowlisted client SGs on 5432). Under strict pod-SG mode the listed SGs replace the node SG; both are required. Pod SG id sg-082f60c7858dfadb9 from the mzla-tb-dev pulumi output keycloak_customer_pod_sg_id (platform-infrastructure #569). Applying recreates the dev keycloak pods with the pod SG (brief rolling restart); they still reach the dev RDS (SG allows the VPC CIDR) and gain Neon reachability. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Summary
Assigns a
SecurityGroupPolicyto thekeycloak-customerpods (tb-dev) so they reach Neon over the sharedstalwart-neondb-privatelinkendpoint. The endpoint SG only admits allowlisted client SGs on 5432; platform-infrastructure #569 created the dedicated pod SG (sg-082f60c7858dfadb9) and opened the paths. Under strict pod-SG mode the policy's SGs replace the node SG, so both are listed:sg-07624df6ceb8865ec— EKS control-plane cluster SGsg-082f60c7858dfadb9—mzla-tb-dev-keycloak-customer-pod(Neon PrivateLink client)Effect on merge
ArgoCD applies the policy → the dev keycloak pods recreate with the pod SG (brief rolling restart). They still reach the dev RDS (its SG allows the VPC CIDR) and gain Neon reachability — which then unblocks the realm backup/restore (and later the repoint to Neon).
Part of #132.
🤖 Generated with Claude Code