Document schema registry connectivity over private endpoints#6324
Open
avinzhang wants to merge 1 commit into
Open
Document schema registry connectivity over private endpoints#6324avinzhang wants to merge 1 commit into
avinzhang wants to merge 1 commit into
Conversation
Clarify that a Kafka ClickPipe's schema registry does not need to be publicly accessible and can be reached over the same reverse private endpoint (AWS PrivateLink / GCP PSC) as the brokers, provided its hostname resolves to the endpoint's private IPs. Updates both the schema registries page and the AWS PrivateLink page. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
4 Skipped Deployments
|
|
|
|
Docs PR opened: ClickHouse/mintlify-docs-dev#104 Documented that Kafka ClickPipes schema registries can be reached over the same reverse private endpoint as the brokers. Once this PR is merged, we'll do a second pass to capture any additional changes and update the docs PR. |
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
3 participants
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
Clarifies that a Kafka ClickPipe's schema registry can be reached over the same reverse private endpoint (AWS PrivateLink / GCP PSC) as the brokers, and does not need to be publicly accessible. This is currently supported but undocumented, which leads customers to assume private schema registries are unsupported.
What changed
kafka/02_schema-registries.md— adds a Network connectivity section (reached over HTTPS, not public-only, resolves via the reverse private endpoint's private DNS / a custom private DNS mapping, https:// requirement).aws-privatelink.md— adds a note under Supported data sources cross-linking to the schema registries page.🤖 Generated with Claude Code
Note
Low Risk
Documentation-only changes with no runtime, security, or data-handling impact.
Overview
Documents that Kafka ClickPipes can reach a schema registry over the same reverse private endpoint as brokers (AWS PrivateLink / GCP PSC), so it does not need to be public.
Adds a Network connectivity section on the schema registries page (HTTPS, private DNS / custom mapping,
https://requirement, setup connectivity check). Adds a cross-linked note under supported data sources on the AWS PrivateLink page.Reviewed by Cursor Bugbot for commit b15809e. Bugbot is set up for automated code reviews on this repo. Configure here.