Skip to content

clickpipes: documentation for GCP-native private networking (PSC)#6409

Open
morsapaes wants to merge 1 commit into
ClickHouse:mainfrom
morsapaes:docs-psc
Open

clickpipes: documentation for GCP-native private networking (PSC)#6409
morsapaes wants to merge 1 commit into
ClickHouse:mainfrom
morsapaes:docs-psc

Conversation

@morsapaes

@morsapaes morsapaes commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

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_mappings is required on GCP, and prerequisites including allowing the clickpipes-production consumer project. Path A walks through Cloud SQL native PSC (gcloud enable/allow list, reading pscServiceAttachmentLink and dnsName, RPE creation in UI/Terraform/API, then wiring a cloudsqlpostgres pipe). Path B covers producer-owned PSC (private-network Cloud SQL or self-managed Postgres) with the gcp-cloud-sql-private-network-psc Terraform module and optional manual PendingAcceptance approval.

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.

@morsapaes morsapaes requested review from a team as code owners June 17, 2026 08:02
@vercel

vercel Bot commented Jun 17, 2026

Copy link
Copy Markdown

@morsapaes is attempting to deploy a commit to the ClickHouse Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant