Skip to content

Conversation

@ginkgoch
Copy link

First-time contributors' checklist

What is changed, added or deleted? (Required)

Which TiDB version(s) do your changes apply to? (Required)

  • Add improved private link for changefeed document
  • Add changefeed private link setup guide for MySQL
  • Modify current changefeed private link setup guide for Kafka

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

  • master (the latest development version)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 versions)
  • v8.1 (TiDB 8.1 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)

What is the related PR or file link(s)?

  • This PR is translated from:
  • Other reference link(s):

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@ti-chi-bot ti-chi-bot bot added contribution This PR is from a community contributor. first-time-contributor Indicates that the PR was contributed by an external member and is a first-time contributor. needs-ok-to-test Indicates a PR created by contributors and need ORG member send '/ok-to-test' to start testing. labels Oct 17, 2025
@ti-chi-bot
Copy link

ti-chi-bot bot commented Oct 17, 2025

Hi @ginkgoch. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@ti-chi-bot ti-chi-bot bot added the missing-translation-status This PR does not have translation status info. label Oct 17, 2025
@gemini-code-assist
Copy link

Summary of Changes

Hello @ginkgoch, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances and clarifies the documentation for configuring private network connectivity for TiDB Cloud changefeeds. It introduces a unified guide for setting up private endpoints, which is then referenced and integrated into the existing documentation for sinking data to both self-hosted Apache Kafka and MySQL. This change aims to simplify the user experience by providing a consistent and comprehensive approach to private link configurations across different cloud providers and downstream services.

Highlights

  • New Private Endpoint Setup Guide: A dedicated document has been added to guide users through setting up private endpoints for changefeeds, centralizing previously scattered information.
  • Streamlined Kafka Private Link Configuration: The process for configuring changefeeds to Apache Kafka via private links has been simplified, now referencing the new private endpoint setup guide.
  • Enhanced MySQL Changefeed Connectivity: New documentation introduces the ability to connect MySQL changefeeds using private endpoints, offering a more secure and private data sinking option.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@ti-chi-bot ti-chi-bot bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Oct 17, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new, centralized document for setting up private endpoints for changefeeds, which simplifies the documentation for Kafka and MySQL sinks. The changes are a positive step towards better organization. My review focuses on improving clarity, consistency, and adherence to the style guide. I've provided suggestions for using sentence case in titles, employing active voice, ensuring consistent terminology, and correcting minor typos and formatting issues to enhance the overall quality of the documentation.

<div label="Private Endpoint">
Private Connect leverages **Private Link** or **Private Service Connect** technologies from cloud providers to enable resources in your VPC to connect to services in other VPCs using private IP addresses, as if those services were hosted directly within your VPC.

- Ensure your MySQL service is connective though private endpoint. Provide the following information in the TiDB Cloud console to create the changefeed:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

There's a typo here. 'connective though' should be 'connectable through'. Also, the sentence can be rephrased to be more direct and use active voice, as recommended by the style guide.1

Suggested change
- Ensure your MySQL service is connective though private endpoint. Provide the following information in the TiDB Cloud console to create the changefeed:
- To connect through a private endpoint, provide the following information in the TiDB Cloud console to create the changefeed:

Style Guide References

Footnotes

  1. Repository Style Guide, lines 22, 43-45: Write in second person ("you") and avoid passive voice.

* If using **VPC Peering** or **Public IP**, fill in your MySQL endpoint.
* If using **Private Endpoint**, select the **Sink Private Endpoint** which is prepared in the [Network](#network) section.

4. Fill in the MySQL endpoints, user name, and password in **MySQL Connection**.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Since the MySQL endpoint is already provided in step 3 for VPC Peering/Public IP, and a Sink Private Endpoint is used for the other option, asking for 'MySQL endpoints' again here is redundant and confusing. It's better to only ask for the credentials.

Suggested change
4. Fill in the MySQL endpoints, user name, and password in **MySQL Connection**.
4. Fill in the user name and password in **MySQL Connection**.

Comment on lines 2 to 3
title: Setup Private Endpoint for Changefeed
summary: Learn how to setup a private endpoint for Changefeed.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

According to the style guide, titles should use sentence case.1 Also, 'setup' as a verb should be two words ('set up'), and 'Changefeed' should be lowercase for consistency with other documents.2

Suggested change
title: Setup Private Endpoint for Changefeed
summary: Learn how to setup a private endpoint for Changefeed.
title: Set up a private endpoint for changefeed
summary: Learn how to set up a private endpoint for changefeed.

Style Guide References

Footnotes

  1. Repository Style Guide, line 32: Use sentence case for headings (e.g., ## Configure the cluster).

  2. Repository Style Guide, line 25: Use consistent terminology.

summary: Learn how to setup a private endpoint for Changefeed.
---

# Setup Private Endpoint for Changefeed

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

According to the style guide, headings should use sentence case.1 Also, 'Setup' as a verb should be two words ('set up'), and 'Changefeed' should be lowercase for consistency.2

Suggested change
# Setup Private Endpoint for Changefeed
# Set up a private endpoint for changefeed

Style Guide References

Footnotes

  1. Repository Style Guide, line 32: Use sentence case for headings (e.g., ## Configure the cluster).

  2. Repository Style Guide, line 25: Use consistent terminology.

3. Fill in the **Service Attachment** that you have configured in [Setup Self Hosted Kafka Private Service Connect in Google Cloud](/tidb-cloud/setup-self-hosted-kafka-private-service-connect.md)
4. Fill in the **Bootstrap Ports**. It is recommended that you provide more than one port. You can use commas `,` to separate multiple ports.
5. Select an **Authentication** option according to your Kafka authentication configuration.
2. Select the **Sink Private Endpoint** which is prepared in the [Network](#network) section.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

To follow the style guide's preference for active voice, it's better to rephrase 'which is prepared'.1

Suggested change
2. Select the **Sink Private Endpoint** which is prepared in the [Network](#network) section.
2. Select the **Sink Private Endpoint** that you prepared in the [Network](#network) section.

Style Guide References

Footnotes

  1. Repository Style Guide, lines 22, 43-45: Write in second person ("you") and avoid passive voice.

</div>
</SimpleTab>

## Step 1. Open the Private Endpoint for Changefeed

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

This heading is a bit ambiguous. A clearer heading that describes the action would be better. Also, headings should be in sentence case per the style guide.1

Suggested change
## Step 1. Open the Private Endpoint for Changefeed
## Step 1. Open the private endpoint creation page

Style Guide References

Footnotes

  1. Repository Style Guide, line 32: Use sentence case for headings (e.g., ## Configure the cluster).

2. Navigate to the cluster overview page of the TiDB cluster, then click **Settings** > **Networking**.
3. Click **Create Private Endpoint** in the **Private Endpoint for Changefeed** section.

## Step 2. Configure the Private Endpoint for Changefeed

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

According to the style guide, headings should use sentence case.1

Suggested change
## Step 2. Configure the Private Endpoint for Changefeed
## Step 2. Configure the private endpoint for changefeed

Style Guide References

Footnotes

  1. Repository Style Guide, line 32: Use sentence case for headings (e.g., ## Configure the cluster).


3. Enter the **Endpoint Service Name** that you configured in [Set Up Self-Hosted Kafka Private Link Service in AWS](https://docs.pingcap.com/tidbcloud/setup-aws-self-hosted-kafka-private-link-service/).

4. Select the **Number of Availability Zones**. Make sure you select the same **Number of AZs** and **AZ IDs** as your Kafka deployment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

The style guide recommends direct instructions.1 Rephrasing 'Make sure you select' to a more direct command would be better.

Suggested change
4. Select the **Number of Availability Zones**. Make sure you select the same **Number of AZs** and **AZ IDs** as your Kafka deployment.
4. Select the **Number of Availability Zones**. Ensure the **Number of AZs** and **AZ IDs** are the same as your Kafka deployment.

Style Guide References

Footnotes

  1. Repository Style Guide, line 22: Write in second person ("you") when addressing users.


2. Enter a **Name** for this **Private Endpoint**.

3. Enter the **Service Attachment** that you configured in [Setup Self Hosted Kafka Private Service Connect in Google Cloud](https://docs.pingcap.com/tidbcloud/setup-self-hosted-kafka-private-service-connect/).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

For consistency, 'Setup' should be 'Set up' to match the verb form used elsewhere. While this is part of a link to another document, it's good practice to maintain consistency across the documentation set.

Suggested change
3. Enter the **Service Attachment** that you configured in [Setup Self Hosted Kafka Private Service Connect in Google Cloud](https://docs.pingcap.com/tidbcloud/setup-self-hosted-kafka-private-service-connect/).
3. Enter the **Service Attachment** that you configured in [Set up Self Hosted Kafka Private Service Connect in Google Cloud](https://docs.pingcap.com/tidbcloud/setup-self-hosted-kafka-private-service-connect/).

Comment on lines 122 to 125




Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

These trailing blank lines are unnecessary and can be removed to improve file cleanliness.


## Restrictions

- Only Organization Owner and Project Owner roles can create private endpoints for changefeeds.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now the project dev role also has the permission.

ginkgoch and others added 6 commits October 17, 2025 15:31
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@ti-chi-bot
Copy link

ti-chi-bot bot commented Oct 17, 2025

@WangLe1321: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@qiancai qiancai self-assigned this Oct 17, 2025
@qiancai qiancai added area/tidb-cloud This PR relates to the area of TiDB Cloud. translation/doing This PR's assignee is translating this PR. translation/no-need No need to translate this PR. and removed missing-translation-status This PR does not have translation status info. translation/doing This PR's assignee is translating this PR. labels Oct 17, 2025
@ginkgoch ginkgoch changed the title DM-11841: Add cdc improved private link document. Add cdc improved private link document. Oct 17, 2025
@qiancai qiancai force-pushed the dm-11841-cdc-private-link-improve branch from 91a43ae to ffa3906 Compare October 21, 2025 03:13
github-actions bot pushed a commit to qiancai/pingcap-docsite-preview that referenced this pull request Oct 21, 2025
@ti-chi-bot ti-chi-bot bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Oct 21, 2025
@ti-chi-bot ti-chi-bot bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Oct 22, 2025
@ti-chi-bot
Copy link

ti-chi-bot bot commented Oct 22, 2025

[LGTM Timeline notifier]

Timeline:

  • 2025-10-21 06:02:57.156328877 +0000 UTC m=+765283.233581447: ☑️ agreed by hfxsd.
  • 2025-10-22 01:11:29.602752688 +0000 UTC m=+834195.680005248: ☑️ agreed by qiancai.

@qiancai
Copy link
Collaborator

qiancai commented Oct 22, 2025

/approve

@ti-chi-bot
Copy link

ti-chi-bot bot commented Oct 22, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiancai

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added the approved label Oct 22, 2025
@qiancai
Copy link
Collaborator

qiancai commented Oct 22, 2025

/retest

@ti-chi-bot ti-chi-bot bot merged commit 4c1d67f into pingcap:release-8.5 Oct 22, 2025
8 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved area/tidb-cloud This PR relates to the area of TiDB Cloud. contribution This PR is from a community contributor. first-time-contributor Indicates that the PR was contributed by an external member and is a first-time contributor. lgtm needs-ok-to-test Indicates a PR created by contributors and need ORG member send '/ok-to-test' to start testing. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. translation/no-need No need to translate this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants