clickpipes: documentation for GCP-native private networking (PSC)#6409
Open
morsapaes wants to merge 1 commit into
Open
clickpipes: documentation for GCP-native private networking (PSC)#6409morsapaes wants to merge 1 commit into
morsapaes wants to merge 1 commit into
Conversation
|
@morsapaes is attempting to deploy a commit to the ClickHouse Team on Vercel. A member of the Team first needs to authorize it. |
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
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
Work-in-progress for PSC integration documentation.
Note
Low Risk
Documentation-only addition with no application or infrastructure code changes.
Overview
Adds a new integration guide at
docs/integrations/data-ingestion/clickpipes/gcp-psc/postgres.md(slug/integrations/clickpipes/gcp-psc/postgres) documenting GCP Private Service Connect for Postgres CDC ClickPipes via Reverse Private Endpoints (GCP_PSC_SERVICE_ATTACHMENT).The page explains how RPEs consume customer-published PSC service attachments, why
custom_private_dns_mappingsis required on GCP, and prerequisites including allowing theclickpipes-productionconsumer project. Path A walks through Cloud SQL native PSC (gcloudenable/allow list, readingpscServiceAttachmentLinkanddnsName, RPE creation in UI/Terraform/API, then wiring acloudsqlpostgrespipe). Path B covers producer-owned PSC (private-network Cloud SQL or self-managed Postgres) with thegcp-cloud-sql-private-network-pscTerraform module and optional manualPendingAcceptanceapproval.It also documents RPE lifecycle in the UI, same-region constraints, and limitations (no VPC peering). Supported GCP regions still has a publish-blocking TODO to paste the region list; the UI steps repeat numbering at item 2.
Reviewed by Cursor Bugbot for commit f9f11ed. Bugbot is set up for automated code reviews on this repo. Configure here.